Governed MCP retrieval and release-flow guide

Synthetic worked example

Discover capability before requesting evidence

How should an agent decide whether a Maha tool can serve its task?

Read public capability and boundary documents first; discovery describes a tool but grants no entitlement.

Starting inputs

A machine task

Public MCP discovery

A maximum acceptable capability

No credential in the prompt

Ordered execution

Work the example

  1. 1

    Read the public method and capability boundaries.

  2. 2

    Compare the task with the declared tool contract.

  3. 3

    Reject non-fit and high-stakes uses.

  4. 4

    Request entitlement only for the exact tool.

  5. 5

    Keep runtime availability separate from documentation.

Expected outputs

  • A fit or non-fit decision
  • The exact requested capability
  • A list of unresolved commercial prerequisites

Verification checks

  • No tool call occurs during discovery.
  • No credential enters a public artifact.
  • A non-fit task terminates before entitlement.

Fail closed

Refusal conditions

  • Discovery is treated as authorization.
  • A private endpoint is guessed.
  • A broad credential is requested.

Digest-bound public fixture

Check the expected state

This fixture contains synthetic operational fields only. Its digest establishes fixture integrity, not scientific truth or a completed commercial transaction.

{
  "artifactKind": "licensed-delivery",
  "schemaVersion": "maha-licensed-evidence/1.0",
  "input": {
    "phase": "discovery",
    "requestedTool": "evidence.retrieve_released_record"
  },
  "expected": {
    "executionCreated": false,
    "entitlementGranted": false
  },
  "artifactSha256": "sha256:4b6c2d281f3ed9a5dcab75a553c6b7192a5caa51ad78d7971d3f5b9b45074858"
}