Permanently delete an item from a 1Password vault. This action cannot be undone.
AI agents call item_delete to permanently remove resources in 1password — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Destructive operations that permanently erase data from credential vaults represent the highest security risk. An agent misusing this tool could irreversibly delete critical passwords, authentication tokens, or other sensitive items stored in 1Password, leading to complete loss of access to accounts and systems. The permanent nature and impossibility of recovery make this critical severity.
From the tool's definition Tool description explicitly states 'Permanently delete an item from a 1Password vault' and 'This action cannot be undone' — classic destructive operation. The tool name 'item_delete' also directly indicates deletion.
Documented attack patterns abuse exactly the kind of access item_delete 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 item_delete:
{
"version": "1",
"default": "deny",
"hide": [
"item_delete"
]
} item_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently delete an item from a 1Password vault. This action cannot be undone. It is categorised as a Destructive tool in the 1password MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 1password MCP server in PolicyLayer and add a rule for item_delete: 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.
item_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the item_delete 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 item_delete. 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.
item_delete 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.