Create a new password/login item in a 1Password vault with optional username, URL, tags, and notes.
AI agents use password_create to create or update resources in 1password — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1password environment.
This tool creates new password entries in 1Password vaults, which is a reversible data modification (Write category). While the blast radius is significant (an agent could create unwanted credential entries, potentially for credential stuffing or impersonation), it does not involve deletion (Destructive), financial transactions (Financial), or arbitrary code execution (Execute).
From the tool's definition Tool description states 'Create a new password/login item in a 1Password vault' — the verb 'create' is a write operation that adds new sensitive credentials to a vault.
Documented attack patterns abuse exactly the kind of access password_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 1password, and nothing reaches the server without passing your rules. This is the rule we recommend for password_create:
{
"version": "1",
"default": "deny",
"tools": {
"password_create": {
"limits": [
{
"counter": "password_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}password_create 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.
Create a new password/login item in a 1Password vault with optional username, URL, tags, and notes. 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_create: 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_create 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_create 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_create. 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_create 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.
Start from 1password, 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.
8 1password tools catalogued and risk-classified — across an index of 43,000+ MCP servers.