The permission boundary behind every agent action
An agent can only be evaluated in the context of what its tools allow. Examine identity, delegated authority and action boundaries before you put a workflow in motion.
Threats, controls and review methods for systems that read untrusted content and act through tools.
An agent can only be evaluated in the context of what its tools allow. Examine identity, delegated authority and action boundaries before you put a workflow in motion.
A computer-use agent treats pixels, accessibility data and interface state as both evidence and an action surface. Security must bind intent to effects beyond the screen.
Legal agents can organize evidence and prepare work, but professional judgement, client authority and verified legal positions cannot be delegated by interface.
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.
Investigators need more than chat transcripts. Preserve identity, instructions, retrieved context, model and tool versions, policy decisions, credentials, network events and actual state changes.
A useful tabletop follows one plausible agent failure through detection, containment, evidence, business recovery and accountable return to service.
“Internet access” is too broad a permission for an agent. Define destinations, protocols, data-release rules and failure behaviour, then test bypasses against the deployed network path.
Maintenance agents can turn condition signals into coordinated work, but plant safety and control demand bounded action and field verification.
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.
A passing patch is only the start. Repository evaluation should test understanding, change quality, security, reviewability and recovery.
Protocols make tools and agents interoperable, but they also standardise discovery, delegation and context exchange. Those interfaces need explicit trust and policy controls.
Review an MCP server as a privileged protocol adapter: verify tool semantics, OAuth boundaries, token audience, downstream delegation, input handling, isolation, logging and consent.
KEEP EXPLORING
Read the method, assumptions and questions to ask.
A little more clarity
Start with the questions that shape a better decision.
The blog examines where agents create business value, how teams define release evidence, how authority and tool access should be bounded, and how engineering, security and governance owners can make a shared decision.
They are written for product, engineering, AI platform, security, governance and transformation leaders responsible for moving an agent workflow from idea or pilot towards accountable operation.
Articles explain the problems and decision methods behind the consultancy’s service direction. They are educational material and do not replace a scoped review of an organisation’s actual system.