theprotocol_logTegDispute

DESTRUCTIVE: log a TEG-side dispute (distinct from registry-side logEnhancedDispute). Agent JWT.

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

Critical RISK CLASS

Category Destructive

Parameters 93 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What theprotocol_logTegDispute does on TheProtocol — Sovereign AI Agent Platform

AI agents call theprotocol_logTegDispute to permanently remove resources in TheProtocol — Sovereign AI Agent Platform, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required
`agent_jwt`	string	—
`reason_code`	string	Yes
`evidence_pointer`	string	—
`brief_description`	string	Yes
`avtp_transaction_id`	string	—
`defendant_agent_did`	string	Yes
`related_transaction_id`	string	—
`dispute_reason_category`	string	—
`evidence_description_or_url`	string	—

Parameters from the server's own tool schema.

RISK

Why theprotocol_logTegDispute is rated Critical

The tool is explicitly labeled DESTRUCTIVE in its description. Logging a formal dispute in a TEG (Token Escrow/Governance) system is an irreversible on-chain or platform action that commits a dispute record, potentially freezing funds or triggering governance processes that cannot be undone. The financial/governance context (staking, transfers mentioned in server description) elevates severity.

From the tool's definition DESTRUCTIVE: log a TEG-side dispute (distinct from registry-side logEnhancedDispute)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

theprotocol_logTegDispute Hidden

theprotocol_logTegDispute is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "theprotocol_logTegDispute"
  ]
}

RESTRICT 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_logTegDispute call is checked against it from then on.

FAQ

Questions about theprotocol_logTegDispute

What does the theprotocol_logTegDispute tool do? +

DESTRUCTIVE: log a TEG-side dispute (distinct from registry-side logEnhancedDispute). Agent JWT. It is categorised as a Destructive tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does theprotocol_logTegDispute accept? +

theprotocol_logTegDispute accepts 9 parameters: agent_jwt, reason_code, evidence_pointer, brief_description, avtp_transaction_id, defendant_agent_did, related_transaction_id, dispute_reason_category, evidence_description_or_url. Required: reason_code, brief_description, defendant_agent_did. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on theprotocol_logTegDispute? +

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

theprotocol_logTegDispute is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit theprotocol_logTegDispute? +

Yes. Add a rate_limit block to the theprotocol_logTegDispute 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_logTegDispute completely? +

Set action: deny in the PolicyLayer policy for theprotocol_logTegDispute. 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_logTegDispute? +

theprotocol_logTegDispute 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern infrastructure agents →Blast radius →Tool call approval →