AI agents use request_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 is a Write action because it modifies system state (creates a verification request/token) and triggers side effects (sending an email). It's reversible and not destructive. Severity is medium because misuse could flood users with verification emails, impact email systems, or be exploited for spam/denial-of-service, but it doesn't delete data, move money, or execute arbitrary code.
From the tool's definition Tool name 'request_verification' and description 'Request email verification' indicate the tool creates or modifies state by initiating a verification flow, likely generating and sending verification tokens or emails.
Documented attack patterns abuse exactly the kind of access request_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 request_verification:
{
"version": "1",
"default": "deny",
"tools": {
"request_verification": {
"limits": [
{
"counter": "request_verification_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}request_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.
Request email verification. 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 request_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.
request_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 request_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 request_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.
request_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.