submit_proof · Tether Name MCP: Risk & Policy

WHAT IT DOES

What submit_proof does on Tether Name

AI agents invoke submit_proof to trigger actions in Tether Name. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why submit_proof needs a policy

This tool submits data to an external API to trigger a verification process. It is not a simple read (it causes state changes on the remote service), not purely a write (it executes a verification workflow), and not destructive or financial. The closest category is Execute, as it triggers an external operation whose outcome depends on the submitted arguments.

From the tool's definition 'Submit a signed proof for a challenge to the tether.name API for verification' — triggers an external API operation (verification submission) with side effects depending on the proof/challenge arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_proof Rate-limited

submit_proof stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_proof": {
      "limits": [
        {
          "counter": "submit_proof_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tether Name, so you can run agents against it safely.

FAQ

Questions about submit_proof

What does the submit_proof tool do? +

Submit a signed proof for a challenge to the tether.name API for verification. It is categorised as a Execute tool in the Tether Name MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submit_proof? +

Register the Tether Name MCP server in PolicyLayer and add a rule for submit_proof: 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 Tether Name. Nothing to install.

What risk level is submit_proof? +

submit_proof is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit submit_proof? +

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

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

submit_proof is provided by the Tether Name MCP server (tether-name-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.