Permission-aware retrieval: the control most RAG diagrams omit
A retrieval system should establish the active principal and filter authorised resources before similarity ranking or model context assembly.
Identity, credentials, authorisation and delegated authority for agents.
A retrieval system should establish the active principal and filter authorised resources before similarity ranking or model context assembly.
Agent credentials should be shorter-lived than the assumptions that justify them. Bind them to a workload, audience, task and action, then prove renewal and revocation work.
Least privilege for agents is not a smaller role assigned once. It is authority narrowed by identity, task, resource, action, time and consequence at every tool call.
Most APIs authenticate well and authorise badly. The defects that matter are object-level and function-level access rules scattered across handlers, where no single reviewer can see the whole rule.
Protocols make tools and agents interoperable, but they also standardise discovery, delegation and context exchange. Those interfaces need explicit trust and policy controls.
Keep sensitive data under client control by moving approved methods and people to the environment, exporting only the minimum reviewed evidence needed for collaboration.
Review an MCP server as a privileged protocol adapter: verify tool semantics, OAuth boundaries, token audience, downstream delegation, input handling, isolation, logging and consent.
A useful agent threat model follows data, instructions, identity, tools and state across trust boundaries. This method turns the map into test cases and control decisions.
A procurement agent may discover, compare and prepare, but supplier commitments require explicit mandates, separation and evidence.
A sandbox limits what compromised execution can reach. Authorisation decides what an authenticated actor may do. Secure agents need both, tested independently and together.
Better agent context is not the largest possible context. It is the smallest authorised, relevant and timely data set that supports the task.
Stopping one process may leave tools, queued actions, delegated agents and credentials active. Define the safe state, control every action path and rehearse the stop under load.
KEEP EXPLORING
Read the method, assumptions and questions to ask.