vault_permissions_grant_group · Mcp 1password MCP

WHAT IT DOES

What vault_permissions_grant_group does on Mcp 1password

AI agents use vault_permissions_grant_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_grant_group needs a policy

This tool modifies access control by granting group-level permissions on a vault. It is reversible (permissions can be revoked), so it falls under Write rather than Destructive. However, the blast radius is high because granting permissions to a group on a 1Password vault could expose all secrets within that vault to unauthorized parties, making it a significant security risk if misused.

From the tool's definition Grant group permissions on a vault. Requires a reason and permission-mutation acknowledgement.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vault_permissions_grant_group Rate-limited

vault_permissions_grant_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_grant_group": {
      "limits": [
        {
          "counter": "vault_permissions_grant_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_grant_group

What does the vault_permissions_grant_group tool do? +

Grant group permissions on a vault. Requires a reason and permission-mutation acknowledgement. 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_grant_group? +

Register the Mcp 1password MCP server in PolicyLayer and add a rule for vault_permissions_grant_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_grant_group? +

vault_permissions_grant_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_grant_group? +

Yes. Add a rate_limit block to the vault_permissions_grant_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_grant_group completely? +

Set action: deny in the PolicyLayer policy for vault_permissions_grant_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_grant_group? +

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