AI agents use pass__generate_password to create or update resources in Proton-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proton-MCP environment.
The primary action is generating (creating) a password artifact within Proton Pass. This is a Write operation since it produces new data. The severity is low because password generation itself has no destructive consequences—generated passwords can be discarded, regenerated, or replaced.
From the tool's definition Tool generates a random password and stores/returns it, which is a reversible creation action. The description states 'Generate a random password using Proton Pass', indicating the tool creates new password data within the password manager.
Documented attack patterns abuse exactly the kind of access pass__generate_password gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proton-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for pass__generate_password:
{
"version": "1",
"default": "deny",
"tools": {
"pass__generate_password": {
"limits": [
{
"counter": "pass__generate_password_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pass__generate_password 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.
Generate a random password using Proton Pass. It is categorised as a Write tool in the Proton-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proton- MCP server in PolicyLayer and add a rule for pass__generate_password: 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 Proton-MCP. Nothing to install.
pass__generate_password 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 pass__generate_password 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 pass__generate_password. 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.
pass__generate_password is provided by the Proton- MCP server (jorgenclaw/proton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proton-MCP, 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.
36 Proton-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.