AI agents use request_email_change 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.
The tool requests an email change, which creates or modifies user account data. This is a Write operation because it initiates a reversible change to stored user information. It is not Execute (no arbitrary code execution), not Destructive (the change can be cancelled or reversed), and not Financial.
From the tool's definition Tool name is 'request_email_change' and description states 'Request email change'. This initiates a modification to user account data (email address) that is reversible through subsequent confirmation or cancellation steps.
Documented attack patterns abuse exactly the kind of access request_email_change 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_email_change:
{
"version": "1",
"default": "deny",
"tools": {
"request_email_change": {
"limits": [
{
"counter": "request_email_change_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}request_email_change 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 change. 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_email_change: 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_email_change 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_email_change 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_email_change. 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_email_change 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.