#permissions
Every post tagged "permissions".
28 posts · showing 11–20
-
Security Review When Nobody Wrote the Code
Human vulnerabilities carry a tell — hurried code, an obvious shortcut. Generated code is uniformly careful-looking, so scanning for the suspicious part stops working. But its consistency cuts both ways.
-
Accountability Cannot Be Delegated to a Model
"The agent decided" answers nothing — not legally, not organizationally, not to the person affected. What accountability actually requires has design consequences, including why a rubber-stamp gate is worse than none.
-
Raw SQL or Curated Queries? Giving an Agent Your Database
A two-line tool description can hand an agent unbounded access to your data and your query planner. The guardrails matter more than the choice — and one cheap planner call prevents most of the damage.
-
Progressive Disclosure: Give the Agent Tools As It Needs Them
The tool list is a per-call parameter, not a fixed property. Withhold the write tools until acting is authorized and a compromised context has nothing dangerous to reach for — enforcement, not instruction.
-
Least Privilege for Agent Credentials
Since injection isn't fully preventable, the credential decides whether a compromise is an inconvenience or an incident. Four scoping dimensions — and the one nobody uses is usually the highest-value.
-
Audit Logs That Survive an Incident
Audit logs get designed for compliance and used during incidents. One question — who caused what, to whom, under what authority — decides every field, and most logs can't answer the authority part.
-
The File System as a Tool: Underrated Agent Infrastructure
Four hundred thousand rows won't fit in a context window; a path and a preview cost nothing. A scoped directory solves large results, durable state, and reviewable artifacts at once — if you resolve paths correctly.
-
State Machines for Agents in Regulated Flows
When doing steps out of order is a compliance failure regardless of outcome, a model-decided control flow is the wrong shape. Put the ordering in code, the conversation in the agent, and scope the tools per state.
-
Multi-Tenancy for Agent Products: The Boundaries That Must Hold
Data, memory, context, and capacity — four boundaries, and two of them are agent-specific enough that no existing multi-tenancy checklist mentions them. Few-shot examples harvested from production are a leak.
-
Data Exfiltration Paths You Forgot Your Agent Had
A URL fetch sends data in the request. A rendered markdown image leaks from the viewer's browser, bypassing every tool-level control. Enumerate the paths — several of them look like features.