theprotocol_getMyDisputes
List disputes (developer-tier view). Optional filters: status, defendant_did, complainant_did.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getmydisputes.md
What theprotocol_getMyDisputes does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getMyDisputes 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 |
|---|---|---|---|
limit | integer | — | |
offset | integer | — | |
defendant_did | string | — | |
dispute_status | string | — | Status filter (e.g. 'open', 'resolved') |
complainant_did | string | — |
Parameters from the server's own tool schema.
Why theprotocol_getMyDisputes is rated Low
This tool retrieves and filters existing dispute records with no side effects. The parameters are all for filtering/querying, not for creating, modifying, or deleting disputes. The 'developer-tier view' qualifier suggests role-based access to read data, which is consistent with Read category.
From the tool's definition Tool name includes 'get' and description states 'List disputes' with optional read-only filters (status, defendant_did, complainant_did). The phrase 'developer-tier view' indicates retrieval of existing data, not modification or execution.
Attacks that exploit this kind of access
The rule that runs theprotocol_getMyDisputes 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_getMyDisputes, this is the rule to start with:
theprotocol_getMyDisputes 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_getMyDisputes call is checked against it from then on.
Questions about theprotocol_getMyDisputes
List disputes (developer-tier view). Optional filters: status, defendant_did, complainant_did. 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_getMyDisputes accepts 5 parameters: limit, offset, defendant_did, dispute_status, complainant_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_getMyDisputes: 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_getMyDisputes 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_getMyDisputes 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_getMyDisputes. 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_getMyDisputes 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