theprotocol_getAgentContracts
List contracts associated with a given agent DID. Optional role filter (client/upgrader). Requires agent JWT.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getagentcontracts.md
What theprotocol_getAgentContracts does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getAgentContracts to retrieve information from TheProtocol — Sovereign AI Agent Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | — | |
agent_did | string | Yes | Target agent DID |
agent_jwt | string | — |
Parameters from the server's own tool schema.
Why theprotocol_getAgentContracts is rated Low
This tool queries and retrieves contract data associated with an agent without modifying, executing, or deleting anything. The optional role filter is a query parameter that narrows results. The severity is low because listing contracts is informational only—misuse by an AI agent would reveal metadata but not alter system state or trigger financial transfers.
From the tool's definition Tool description explicitly states 'List contracts' which is a retrieval operation with no modification. The requirement for agent JWT is an authentication control, not a side effect.
Attacks that exploit this kind of access
The rule that runs theprotocol_getAgentContracts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TheProtocol — Sovereign AI Agent Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For theprotocol_getAgentContracts, this is the rule to start with:
theprotocol_getAgentContracts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_getAgentContracts call is checked against it from then on.
Questions about theprotocol_getAgentContracts
List contracts associated with a given agent DID. Optional role filter (client/upgrader). Requires agent JWT. It is categorised as a Read tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it retrieves data without modifying state.
theprotocol_getAgentContracts accepts 3 parameters: role, agent_did, agent_jwt. Required: agent_did. The full parameter table on this page comes from the server's own tool schema.
Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_getAgentContracts: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches TheProtocol — Sovereign AI Agent Platform. Nothing to install.
theprotocol_getAgentContracts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the theprotocol_getAgentContracts rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for theprotocol_getAgentContracts. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
theprotocol_getAgentContracts is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.
Across the catalogue