Low Risk

resend_verification

Resend the email verification link for an existing Unphurl account. Use this when a user signed up but their verification link expired (links are valid for 24 hours) and they need a new one. The user's API key won't work until their email is verified. For security, the response is always the sa...

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

AI agents call resend_verification to retrieve information from Unphurl 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 resend_verification 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.

unphurl.yaml
tools:
  resend_verification:
    rules:
      - action: allow

See the full Unphurl policy for all 13 tools.

Tool Name resend_verification
Category Read
MCP Server Unphurl MCP Server
Risk Level Low

View all 13 tools →

Agents calling read-class tools like resend_verification have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the resend_verification tool do? +

Resend the email verification link for an existing Unphurl account. Use this when a user signed up but their verification link expired (links are valid for 24 hours) and they need a new one. The user's API key won't work until their email is verified. For security, the response is always the same regardless of whether the email exists, is already verified, or was rate limited. This prevents account enumeration. Rate limited to 3 requests per email per hour. This tool does not require an API key.. It is categorised as a Read tool in the Unphurl MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on resend_verification? +

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

What risk level is resend_verification? +

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

Can I rate-limit resend_verification? +

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

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

resend_verification is provided by the Unphurl MCP server (@unphurl/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Unphurl

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.