Revoke all group permissions from a vault. Requires a reason and permission-mutation acknowledgement.
AI agents call vault_permissions_revoke_group to permanently remove resources in Mcp 1password — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking all group permissions from a vault is an irreversible access-control action that removes a group's ability to access the vault. This cannot be passively undone without explicitly re-granting permissions, and misuse could lock out users from critical secrets stored in the vault. The 'all permissions' scope makes the blast radius high.
From the tool's definition Revoke all group permissions from a vault
Attacks that exploit this kind of access
Revoke all group permissions from a vault. Requires a reason and permission-mutation acknowledgement. It is categorised as a Destructive tool in the Mcp 1password MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp 1password MCP server in PolicyLayer and add a rule for vault_permissions_revoke_group: 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.
vault_permissions_revoke_group 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 vault_permissions_revoke_group 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 vault_permissions_revoke_group. 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.
vault_permissions_revoke_group 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →