password_generate · Mcp 1password MCP: Risk & Policy

WHAT IT DOES

What password_generate does on Mcp 1password

AI agents use password_generate to create or update resources in Mcp 1password — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp 1password environment.

WHY IT NEEDS A POLICY

Why password_generate needs a policy

password_generate creates a new password artifact, which is a data creation action (Write category). It doesn't modify existing data (would be more severe if updating), nor does it delete data (Destructive), execute arbitrary commands (Execute), or move money (Financial).

From the tool's definition Tool generates and returns a password in plaintext for immediate use. The password is a newly created secret asset that persists in the system's context, making this a write operation that creates new data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

password_generate Rate-limited

password_generate 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "password_generate": {
      "limits": [
        {
          "counter": "password_generate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp 1password, so you can run agents against it safely.

FAQ

Questions about password_generate

What does the password_generate tool do? +

Generate a strong random password and return it in plaintext for immediate use. Requires a reason and generated-secret acknowledgement. It is categorised as a Write tool in the Mcp 1password MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on password_generate? +

Register the Mcp 1password MCP server in PolicyLayer and add a rule for password_generate: 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 Mcp 1password. Nothing to install.

What risk level is password_generate? +

password_generate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit password_generate? +

Yes. Add a rate_limit block to the password_generate 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.

How do I block password_generate completely? +

Set action: deny in the PolicyLayer policy for password_generate. 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.

What MCP server provides password_generate? +

password_generate is provided by the Mcp 1password MCP server (kefapps/onepassword-mcp-codex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.