Medium Risk

password_update

Update (rotate) a password or concealed field on an existing 1Password item. If the target field does not exist, it will be created.

Part of the 1password MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@takescake/1password-mcp Write Risk 2/5

AI agents use password_update to create or modify resources in 1password. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call password_update repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach 1password.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-cakerepository-1password.yaml
tools:
  password_update:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full 1password policy for all 8 tools.

Tool Name password_update
Category Write
Risk Level Medium

Agents calling write-class tools like password_update have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the password_update tool do? +

Update (rotate) a password or concealed field on an existing 1Password item. If the target field does not exist, it will be created.. It is categorised as a Write tool in the 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_update? +

Add a rule in your Intercept YAML policy under the tools section for password_update. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the 1password MCP server.

What risk level is password_update? +

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

Can I rate-limit password_update? +

Yes. Add a rate_limit block to the password_update rule in your Intercept 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_update completely? +

Set action: deny in the Intercept policy for password_update. 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_update? +

password_update is provided by the 1password MCP server (@takescake/1password-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on 1password

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.