Low Risk

verify_signature

Verify a message signature and recover the address that signed it. This is used to determine who signed a specific message. Requires the original message and the signature as input. Returns the address that created the signature.

Single-target operation

Part of the COTI MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call verify_signature to retrieve information from COTI MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though verify_signature only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

davibauer-coti-mcp.yaml
tools:
  verify_signature:
    rules:
      - action: allow

See the full COTI MCP Server policy for all 44 tools.

Tool Name verify_signature
Category Read
Risk Level Low

View all 44 tools →

What does the verify_signature tool do? +

Verify a message signature and recover the address that signed it. This is used to determine who signed a specific message. Requires the original message and the signature as input. Returns the address that created the signature.. It is categorised as a Read tool in the COTI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verify_signature? +

Add a rule in your Intercept YAML policy under the tools section for verify_signature. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the COTI MCP Server MCP server.

What risk level is verify_signature? +

verify_signature is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verify_signature? +

Yes. Add a rate_limit block to the verify_signature rule in your Intercept 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 verify_signature completely? +

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

verify_signature is provided by the COTI MCP Server MCP server (davibauer/coti-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on COTI MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.