AI agents use bulk_pin to create or update resources in Fastmail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fastmail MCP Server environment.
Pinning/unpinning emails modifies email state and organization but does not create, delete, or destroy data—the emails remain intact and the operation is reversible (pins can be toggled on/off). This classifies as Write rather than Read (has side effects) or Destructive (reversible).
From the tool's definition Tool name 'bulk_pin' and description 'Pin or unpin multiple emails' indicates modification of email metadata (pin state) affecting multiple messages. This is a write operation that changes email attributes reversibly.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bulk_pin gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fastmail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bulk_pin:
{
"version": "1",
"default": "deny",
"tools": {
"bulk_pin": {
"limits": [
{
"counter": "bulk_pin_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} bulk_pin 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.
Pin or unpin multiple emails. It is categorised as a Write tool in the Fastmail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fastmail MCP Server MCP server in PolicyLayer and add a rule for bulk_pin: 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 Fastmail MCP Server. Nothing to install.
bulk_pin 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 bulk_pin 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 bulk_pin. 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.
bulk_pin is provided by the Fastmail MCP Server MCP server (madllama25/fastmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fastmail 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.
38 Fastmail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.