vault_permissions_update_group · Mcp 1password MCP

WHAT IT DOES

What vault_permissions_update_group does on Mcp 1password

AI agents use vault_permissions_update_group to create or update resources in Mcp 1password — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp 1password environment.

WHY IT NEEDS A POLICY

Why vault_permissions_update_group needs a policy

The tool updates vault permissions by replacing group configuration, which modifies data (group membership and associated permissions) but is not irreversible—groups can be updated again. This falls under Write rather than Execute because it directly modifies a data object rather than triggering external operations.

From the tool's definition Tool named 'vault_permissions_update_group' with description 'Replace a group' indicates modification of group permissions/configuration in 1Password vaults. This is a reversible write operation that changes access control settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vault_permissions_update_group Rate-limited

vault_permissions_update_group 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vault_permissions_update_group": {
      "limits": [
        {
          "counter": "vault_permissions_update_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp 1password, so you can run agents against it safely.

FAQ

Questions about vault_permissions_update_group

What does the vault_permissions_update_group tool do? +

Replace a group. It is categorised as a Write tool in the Mcp 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 vault_permissions_update_group? +

Register the Mcp 1password MCP server in PolicyLayer and add a rule for vault_permissions_update_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.

What risk level is vault_permissions_update_group? +

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

Can I rate-limit vault_permissions_update_group? +

Yes. Add a rate_limit block to the vault_permissions_update_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.

How do I block vault_permissions_update_group completely? +

Set action: deny in the PolicyLayer policy for vault_permissions_update_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.

What MCP server provides vault_permissions_update_group? +

vault_permissions_update_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.