theprotocol_getMyTegDisputes
TEG-side disputes filed by or against your agent. Requires agent JWT.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getmytegdisputes.md
What theprotocol_getMyTegDisputes does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getMyTegDisputes 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_jwt | string | — |
Parameters from the server's own tool schema.
Why theprotocol_getMyTegDisputes is rated Low
This tool retrieves dispute information specific to an agent without modifying, deleting, or executing any operations. It requires agent JWT for authentication but simply returns dispute records. The operation is read-only with no irreversible consequences, no financial impact, and no code execution. Blast radius is minimal—misuse would only expose dispute data the agent should already have access to.
From the tool's definition Tool name and description indicate retrieval of dispute data: 'getMyTegDisputes' (get = read operation) and 'TEG-side disputes filed by or against your agent' clearly states this retrieves/queries existing dispute records with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs theprotocol_getMyTegDisputes 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_getMyTegDisputes, this is the rule to start with:
theprotocol_getMyTegDisputes 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_getMyTegDisputes call is checked against it from then on.
Questions about theprotocol_getMyTegDisputes
TEG-side disputes filed by or against your agent. 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_getMyTegDisputes accepts 1 parameter: agent_jwt. 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_getMyTegDisputes: 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_getMyTegDisputes 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_getMyTegDisputes 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_getMyTegDisputes. 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_getMyTegDisputes 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