resend_verification_code
Resend the email verification code for a trial account. Use this if the user did not receive the code or it expired.
This record as markdown: /tools/adbutler/resend-verification-code.md
What resend_verification_code does on AdButler
AI agents invoke resend_verification_code to trigger actions in AdButler. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | The email address used to create the trial account |
Parameters from the server's own tool schema.
Why resend_verification_code is rated High
This tool triggers an external operation (sending an email) rather than simply reading or writing data. It causes a side effect in an external system (email delivery). The blast radius is low since misuse only results in sending an extra verification email, but it is categorized as Execute because it triggers an external operation whose effects depend on the state of the account.
From the tool's definition 'Resend the email verification code' and 'Use this if the user did not receive the code or it expired'
Attacks that exploit this kind of access
The rule that runs resend_verification_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resend_verification_code, this is the rule to start with:
resend_verification_code 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every resend_verification_code call is checked against it from then on.
Questions about resend_verification_code
Resend the email verification code for a trial account. Use this if the user did not receive the code or it expired. It is categorised as a Execute tool in the AdButler MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
resend_verification_code accepts 1 parameter: email. Required: email. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for resend_verification_code: 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 AdButler. Nothing to install.
resend_verification_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the resend_verification_code 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 resend_verification_code. 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.
resend_verification_code is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdButler, and thousands of servers like it.
Across the catalogue