verify_trial_email
Verify a trial account email with the verification code sent to the user. Call this after create_trial_account. The user must provide the code from their email. On success, the API key is automatically configured.
This record as markdown: /tools/adbutler/verify-trial-email.md
What verify_trial_email does on AdButler
AI agents use verify_trial_email to create or update resources in AdButler, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | The email address used to create the trial account |
verification_code | string | Yes | The verification code from the email |
Parameters from the server's own tool schema.
Why verify_trial_email is rated Medium
This tool verifies an email and configures an API key upon success. It modifies account state (activating a trial account and setting up credentials), which is a reversible write operation. It does not delete data, execute code, or involve financial transactions.
From the tool's definition Verify a trial account email with the verification code sent to the user... On success, the API key is automatically configured.
Attacks that exploit this kind of access
The rule that runs verify_trial_email 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 verify_trial_email, this is the rule to start with:
verify_trial_email stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 verify_trial_email call is checked against it from then on.
Questions about verify_trial_email
Verify a trial account email with the verification code sent to the user. Call this after create_trial_account. The user must provide the code from their email. On success, the API key is automatically configured. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
verify_trial_email accepts 2 parameters: email, verification_code. Required: email, verification_code. 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 verify_trial_email: 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.
verify_trial_email is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the verify_trial_email 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 verify_trial_email. 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.
verify_trial_email 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.
This server
Across the catalogue