theprotocol_getMyAgentDisputes
List disputes where the given agent_did is complainant OR defendant. Requires agent JWT. Pass your own DID for self-disputes.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getmyagentdisputes.md
What theprotocol_getMyAgentDisputes does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getMyAgentDisputes 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 |
|---|---|---|---|
agent_did | string | Yes | |
agent_jwt | string | — |
Parameters from the server's own tool schema.
Why theprotocol_getMyAgentDisputes is rated Low
This tool queries and retrieves dispute records associated with an agent. The operation is read-only (list/retrieval) with no side effects on data integrity. Severity is elevated to 'medium' rather than 'low' because disputes may contain sensitive information about agent interactions, compliance issues, or legal/financial matters that could be misused if an unauthorized agent gains access via a compromised JWT.
From the tool's definition Tool name contains 'get' and description states 'List disputes' — a retrieval operation with no modification or deletion. Requires agent JWT for authentication.
Attacks that exploit this kind of access
The rule that runs theprotocol_getMyAgentDisputes 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_getMyAgentDisputes, this is the rule to start with:
theprotocol_getMyAgentDisputes 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_getMyAgentDisputes call is checked against it from then on.
Questions about theprotocol_getMyAgentDisputes
List disputes where the given agent_did is complainant OR defendant. Requires agent JWT. Pass your own DID for self-disputes. 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_getMyAgentDisputes accepts 2 parameters: 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_getMyAgentDisputes: 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_getMyAgentDisputes 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_getMyAgentDisputes 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_getMyAgentDisputes. 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_getMyAgentDisputes 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