Softlander Book a call
Agent-to-agent interoperability

Protocol authorisation review

Define what an authenticated agent may request through a protocol

Authenticated peers can submit tasks with different business consequences. The decision is how to define what an authenticated agent may request through a protocol. The work begins with your actual workflow and looks for the evidence that separates intended behaviour from a consequential exception. It is particularly relevant to authorisation architects and workflow service owners. A useful outcome is an explicit account of what was examined, what remains uncertain, and which decision the evidence can support.

Book a 30 minute readiness callBrowse this capability group

The interaction contracts relationship

  1. Starting evidenceTask action catalogues

    Establish the basis for peer role.

  2. Decision boundaryTask resource

    Bound operations to the intended object and context.

  3. Decision artefactProtocol authorisation matrix

    Retain the scoped finding and its unresolved dependencies.

Proposed working model. Untested peers require their own compatibility evidence.

Decision

Frame the decision around peer role

Questions and the evidence they need

Criterion / evidencePeer role
Inspect task action catalogues for the relevant constraint or observation.
Criterion / evidenceTask resource
Inspect peer roles for the relevant constraint or observation.
Criterion / evidenceReceiving control
Inspect resource scopes for the relevant constraint or observation.
Read each criterion against the available evidence before deciding that additional work is needed.

The decision is how to define what an authenticated agent may request through a protocol. This is relevant to authorisation architects and workflow service owners when authenticated peers can submit tasks with different business consequences. Name the affected workflow, the consequence of a wrong decision, and the owner who can act on the result. The initial discussion should establish which evidence is already available and which uncertainty is material enough to investigate.

The specific failure hypothesis is that any authenticated peer can request administrative or cross-customer work. It remains a hypothesis until examined in the deployment. Existing internal tests or operating records may already resolve it; identify the uncovered question before commissioning additional work.

Mechanism

An authenticated peer still needs task authority

Relationships within interaction contracts

Source or conditionPeer role
Resolve the caller's verified attributes.
Crossing or choiceTask resource
Bound operations to the intended object and context.
Consequence or decisionReceiving control
Observe permission decisions before task acceptance.
Compare authority and state at the receiving boundary. Each relationship needs evidence in the actual scope.

What this specialty examines

Protocol authorisation should describe the tasks and resources each peer may request. A single endpoint can expose low-consequence queries and administrative operations. Define how action, tenant, purpose and current mandate influence the receiving system’s decision.

The review should model and test peer-task-resource-context decisions at the receiving boundary. Identify the normal route, relevant exceptions and the authoritative record of the outcome. Inspect the relevant business-system record, enforcement event or process evidence alongside any reported status. Keep incomplete cases visible, with an explanation of what their absence prevents the owner from concluding.

The tradeoff to make explicit

For this decision, broad peer access simplifies onboarding while task-specific permission keeps authority explicit. Compare the available design or operating choices against the same intended outcome. If one option removes a required control or changes the task boundary, describe that difference before treating its apparent simplicity, speed or lower effort as an improvement. The decision should expose the tradeoff instead of burying it in an aggregate score.

Preparation

Connect the working inputs to the boundary being examined

Evidence packet for peer role

Illustrative working format

BasisTask action catalogues
Retain the observed conditions and distinguish gaps from contrary evidence.
ContextPeer roles
Identify the accountable role and verify its decision rights or availability.
ObservationResource scopes
Establish permitted access, provenance, and which task conditions it represents.
DependencyEnforcement records
Establish permitted access, provenance, and which task conditions it represents.
Illustrative preparation record. Availability, revision, and handling need confirmation.

Start with task action catalogues, peer roles, resource scopes and enforcement records. Identify the owner, revision and operating context of each source. Sanitised examples may support initial design, but differences from actual conditions should remain explicit. Where direct access is unsuitable, a customer-controlled evidence or execution route may be considered, with agreed handling and retention.

The scope also needs the integration owner, agreed expectations for a representative interaction case, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which any authenticated peer can request administrative or cross-customer work from acceptable behaviour. If stakeholders disagree about intended behaviour, resolve the interpretation before classifying the observed difference as a defect.

How the work proceeds

Carry peer role through to an accountable finding

From the scoped material to a decision record

  1. Establish conditionsTask action catalogues

    Agree the task meaning at the sending boundary.

  2. Examine the relationshipTask resource

    Apply the scoped check to receiving control.

  3. Retain the findingProtocol authorisation matrix

    Record the evidence, open dependencies, and the owner’s next decision.

Proposed sequence; resolve interpretation or access gaps before relying on the next step.

Fix the interaction contract and versions

Assemble task action catalogues, peer roles, resource scopes and enforcement records with authorisation architects and workflow service owners. Identify the participating implementations, interface revisions, authority assumptions and intended business result. Prepare messages and task-state examples from both sides, including an interrupted exchange and a disputed or incomplete outcome. The preparation output is a paired contract fixture showing what each participant expects and which differences would prevent the workflow from completing correctly.

Run and compare both sides of the exchange

Build allowed and denied peer-task cases and inspect enforcement before execution. Include missing context and attempts to expand scope through task parameters. Do not rely entirely on a sending agent to enforce restrictions that protect the receiver’s resources.

Choose the contract or integration change

Summarise the comparison in a protocol authorisation matrix and proposed deny-path cases. Classify each mismatch as interface validation, business meaning, identity, task state or operating behaviour. Decide whether to change a participant, add an explicit adapter rule, narrow supported combinations or defer the connection. Validate the affected pair again and preserve limitations that translation cannot resolve, especially around cancellation, authority and partial completion.

Indicative artefact

Make the protocol authorisation matrix usable by its owner

Protocol authorisation matrix

Illustrative working format

Annotated fieldProtocol authorisation matrix
Identify the assessed workflow, revision, and decision boundary.
Annotated fieldDeny-path cases
Link supporting and contrary observations to inspectable evidence.
Annotated fieldTask resource evidence
Link observations and counterevidence to the case, configuration, and conclusion limit.
Illustrative artefact structure, not a completed engagement or an observed result.

A useful decision artefact is a protocol authorisation matrix and proposed deny-path cases. Supporting material may include selected cases, configuration or process records, evidence references, a disagreement log and prioritised actions. Retain the case selection rationale and material disagreements alongside the result; otherwise the result may be mistaken for complete coverage.

Illustrative scenario

Examine receiving control through a constructed exception

A constructed case and its decision paths

Illustrative scenario

  1. SituationPeer role

    A known peer asks to operate on a resource outside its delegated scope.

  2. Question to examineTask resource

    Check the requested resource against the peer's delegated task scope.

  3. Conditional next actionReceiving control

    Deny the operation even though peer authentication succeeds.

Fictional example. No executed test, customer engagement, or measured outcome is implied.

Consider a fictional situation: a peer allowed to request inventory availability can also invoke a stock-adjustment task exposed by the same endpoint. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.

For inventory availability versus adjustment, test both with the same authenticated peer. The expected difference belongs in task authorisation. A connection that is secure and authenticated can still expose an excessive action set if that policy is absent.

Scope and next action

Keep the conclusion within named implementations and revisions

Confirm fit before the next commitment

Included boundaryPeer role
This review is limited to named implementations and revisions.
PrerequisiteTask action catalogues
The relevant owner must confirm access and the intended operating conditions.
Claim limitProtocol authorisation matrix
Untested peers require their own compatibility evidence.
Bring the triggering change and existing evidence; resolve the dependency that could alter the decision.

Compatibility is assessed for named implementations, versions, features and workflows. It does not establish universal conformance, vendor endorsement or interoperability with untested peers. Any engagement depends on an agreed scope, qualified team, authorised access and confirmed availability. Bring the affected workflow, its current configuration or process, the triggering change and the evidence already available. The immediate scope question is prompted by the situation in which authenticated peers can submit tasks with different business consequences; confirm which missing observation would change the owner’s next action.

Ways to engage

Related engagement scopes

AI Agent Protocol Interoperability Lab

Find where connected agents disagree. Exercise message contracts, identity propagation and failure recovery across your selected integrations.

Read about this offer

Continue exploring

Related insights and resources

Evaluation & assurance6 MIN READ

How to design a joint AI evaluation lab

A joint lab should be a governed way to create decision evidence across organisations, with shared methods but explicit ownership of systems, data and conclusions.

Agent security6 MIN READ

Agent protocols are creating a new control surface

Protocols make tools and agents interoperable, but they also standardise discovery, delegation and context exchange. Those interfaces need explicit trust and policy controls.

Agent security6 MIN READ

A practical security review for an MCP server

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 little more clarity

Questions to consider.

Start with the questions that shape a better decision.

Why is successful authentication insufficient for accepting a task?

Authentication establishes who the peer is under defined assumptions. The receiver must still decide whether that peer may request this task on this resource in the current context.

Which task catalogues define peer permissions?

Start with task action catalogues, peer roles, resource scopes and enforcement records. Record their revision, owner and relationship to the intended workflow. Missing context should be identified before interpreting outcomes; a sanitised fixture is useful only when its relevant differences from the operating case are understood.

How should authenticated but unauthorised tasks be tested?

Model and test peer-task-resource-context decisions at the receiving boundary. Compare both participants' accepted inputs, task states and results under a named interface revision. Include interrupted or delayed interactions. Parser acceptance should not be treated as agreement about business meaning, authority or completion.

What belongs in a protocol authorisation matrix?

The proposed output is a protocol authorisation matrix and proposed deny-path cases. Include the selected conditions, supporting observations, unresolved differences and next decision. A reviewer should be able to follow each important conclusion back to its evidence and understand the limits without depending on an undocumented explanation from the author.

When should resource context be required?

Require resource context whenever permission depends on tenant, assignment, purpose or a particular object. An authenticated peer's general eligibility does not authorise every resource reachable through the endpoint.

What if existing evidence already answers the question?

Review its scope, provenance and configuration before proposing new work. Existing work from authorisation architects and workflow service owners may already be sufficient. In that case, capture the decision, unresolved limitations and the change that would require another review. Additional assessment should address a real gap.

What would make the findings inconclusive?

Missing task action catalogues, peer roles, resource scopes and enforcement records can prevent a reliable interpretation, depending on the case. Record the specific missing observation and its implication. The owner can supply evidence, narrow the claim or defer the dependent decision; an incomplete case should not silently be counted as a pass.

Start with the decision you need to make.

Tell us about the agent workflow you want reviewed, and where you need greater clarity. Scope and availability are confirmed together.

Book a 30 minute readiness call Get the agent release checklist

Connected disciplines

Trust negotiation between agents

Establish what evidence is required before agents rely on each other. The review connects trust policies, identity evidence, capability attestations and exception handling to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.

Cross-agent identity propagation

Preserve actor and tenant context across agent-to-agent handoffs. The review connects identity claims, delegation chains, tenant mappings and downstream audit records to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.

Agent communication privacy

Limit information exchanged between cooperating agents. The review connects message payloads, data classifications, purpose statements and retention settings to a bounded review of agent interaction contracts, giving the integration owner a clearer basis for the next action.