Skip to main content
Glama

Boundra — Payment Approval Gateway for AI Agents

revoke_policy

DestructiveIdempotent

[USER ONLY] Revoke a policy chain (takes effect immediately; subsequent payments default to DENY). Must carry the user's wallet signature over the revocation statement.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "owner": "<owner>",
      "scope": "<scope>",
      "revoked_through": "<revoked_through>",
      "created_at": "<created_at>",
      "signature": "<signature>"
    },
    "name": "revoke_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesOwner wallet address that scopes policy, budget and audit state
scopeYesPolicy scope to revoke: user or agent
agent_idNoOptional agent identifier for agent-scoped policy or attribution
signatureYesOwner wallet signature over the revocation statement
created_atYesRevocation creation time as a Unix timestamp in seconds
revoked_throughYesHighest policy version covered by this revocation

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Optional agent identifier for agent-scoped policy or attribution"
    • addedInput schema / properties / created_at / description
      Added value: +"Revocation creation time as a Unix timestamp in seconds"
    • addedInput schema / properties / owner / description
      Added value: +"Owner wallet address that scopes policy, budget and audit state"
    • addedInput schema / properties / revoked_through / description
      Added value: +"Highest policy version covered by this revocation"
    • addedInput schema / properties / scope / description
      Added value: +"Policy scope to revoke: user or agent"
    • addedInput schema / properties / signature / description
      Added value: +"Owner wallet signature over the revocation statement"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine value beyond that: the effect is immediate, payments fail closed to DENY afterward, and a user wallet signature over the revocation statement is required. It stops short of saying whether a revocation can be undone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the caller restriction front-loaded and the consequence of revocation attached to the action. Nothing is wasted, though the parenthetical packs three distinct facts together.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers the auth requirement and the fail-closed outcome. For a destructive mutation with five required parameters, the remaining gap is reversibility and recovery, which is minor relative to what is stated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every parameter is already documented, and the description's signature sentence largely restates the schema's own wording. No extra syntax or format detail is offered for revoked_through or scope beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Revoke a policy chain') and pairs it with the immediate effect on payments. The '[USER ONLY]' prefix marks the caller class, distinguishing it from agent-mediated flows, though it does not name a sibling tool by way of contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The '[USER ONLY]' tag implies who may call it and the revocation framing implies when, but there is no explicit when-not or named alternative (e.g., use set_policy to replace a chain rather than revoke it). Guidance is present but must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.