theprotocol_getDisputeById
Get a single dispute by id (full record with status, ruling, parties, evidence). Requires developer JWT.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getdisputebyid.md
What theprotocol_getDisputeById does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getDisputeById 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 |
|---|---|---|---|
dispute_id | string | Yes |
Parameters from the server's own tool schema.
Why theprotocol_getDisputeById is rated Low
This tool queries and retrieves dispute information (status, ruling, parties, evidence). It performs a read-only lookup operation with no ability to create, modify, delete, or execute arbitrary actions. The requirement for developer JWT is an access control mechanism, not an indicator of higher risk.
From the tool's definition Tool name contains 'get' and description states 'Get a single dispute by id (full record...)' — retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs theprotocol_getDisputeById 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_getDisputeById, this is the rule to start with:
theprotocol_getDisputeById 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_getDisputeById call is checked against it from then on.
Questions about theprotocol_getDisputeById
Get a single dispute by id (full record with status, ruling, parties, evidence). Requires developer 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_getDisputeById accepts 1 parameter: dispute_id. Required: dispute_id. 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_getDisputeById: 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_getDisputeById 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_getDisputeById 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_getDisputeById. 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_getDisputeById 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