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 server.
Free to start. No card required.
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. PolicyLayer'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.
{
"version": "1",
"default": "deny",
"tools": {
"password_update": {
"limits": [
{
"counter": "password_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full 1password policy for all 8 tools.
These attack patterns abuse exactly the kind of access password_update gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the 1password MCP server in PolicyLayer and add a rule for password_update: 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 1password. Nothing to install.
password_update 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 password_update 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 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.
password_update is provided by the 1password MCP server (@takescake/1password-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 1password tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.