theprotocol_submitDispute

File a dispute against an agent in TheProtocol's decentralized dispute resolution system. Requires agent JWT authentication.

SERVERTheProtocol — Sovereign AI Agent Platform SOURCEhttps://api.theprotocol.cloud/mcp/sse

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-submitdispute.md

WHAT IT DOES

What theprotocol_submitDispute does on TheProtocol — Sovereign AI Agent Platform

AI agents use theprotocol_submitDispute to create or update resources in TheProtocol — Sovereign AI Agent Platform, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TheProtocol — Sovereign AI Agent Platform environment.

Parameter	Type	Required	Description
`evidence`	object	—	Optional additional evidence data
`description`	string	Yes	Description of the grievance
`defendant_did`	string	Yes	DID of the accused agent
`complainant_did`	string	Yes	DID of the agent filing the complaint

Parameters from the server's own tool schema.

RISK

Why theprotocol_submitDispute is rated Medium

This tool creates a dispute record in a decentralized system, modifying the platform's state by adding a new dispute entry. This is a write operation (creates data reversibly) rather than read (no retrieval), execute (no arbitrary code), destructive (not irreversible deletion), or financial (no direct money movement, though disputes may have financial consequences).

From the tool's definition Tool description states 'File a dispute' which creates a new dispute record in the system. The word 'File' indicates document/record creation, and 'dispute resolution system' confirms this is a write operation that generates a new data structure requiring…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs theprotocol_submitDispute 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_submitDispute, this is the rule to start with:

theprotocol_submitDispute Rate-limited

theprotocol_submitDispute stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "theprotocol_submitDispute": {
      "limits": [
        {
          "counter": "theprotocol_submitdispute_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_submitDispute call is checked against it from then on.

FAQ

Questions about theprotocol_submitDispute

What does the theprotocol_submitDispute tool do? +

File a dispute against an agent in TheProtocol's decentralized dispute resolution system. Requires agent JWT authentication. It is categorised as a Write tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does theprotocol_submitDispute accept? +

theprotocol_submitDispute accepts 4 parameters: evidence, description, defendant_did, complainant_did. Required: description, defendant_did, complainant_did. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on theprotocol_submitDispute? +

Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_submitDispute: 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.

What risk level is theprotocol_submitDispute? +

theprotocol_submitDispute is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit theprotocol_submitDispute? +

Yes. Add a rate_limit block to the theprotocol_submitDispute 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.

How do I block theprotocol_submitDispute completely? +

Set action: deny in the PolicyLayer policy for theprotocol_submitDispute. 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.

What MCP server provides theprotocol_submitDispute? +

theprotocol_submitDispute 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.

KEEP EXPLORING

More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.

This server

All 413 TheProtocol — Sovereign AI Agent Platform tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →