Confirm email verification with token
AI agents use confirm_verification to create or update resources in PocketBase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PocketBase MCP Server environment.
This tool modifies user data (marks email as verified) but is reversible and has limited blast radius compared to destructive operations. It requires a valid token, suggesting some protection against misuse. Categorized as Write rather than Execute because it performs a specific database update operation rather than executing arbitrary code.
From the tool's definition Tool name 'confirm_verification' and description 'Confirm email verification with token' indicate a state-changing operation that modifies user verification status in the database.
Documented attack patterns abuse exactly the kind of access confirm_verification gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PocketBase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for confirm_verification:
{
"version": "1",
"default": "deny",
"tools": {
"confirm_verification": {
"limits": [
{
"counter": "confirm_verification_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}confirm_verification 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.
Free to start. No card required.
Confirm email verification with token. It is categorised as a Write tool in the PocketBase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PocketBase MCP Server MCP server in PolicyLayer and add a rule for confirm_verification: 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 PocketBase MCP Server. Nothing to install.
confirm_verification 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 confirm_verification 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 confirm_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.
confirm_verification is provided by the PocketBase MCP Server MCP server (mrwyndham/pocketbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PocketBase MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 PocketBase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.