reapply_anyone_permissions · GAM MCP Server MCP

WHAT IT DOES

What reapply_anyone_permissions does on GAM MCP Server

AI agents use reapply_anyone_permissions to create or update resources in GAM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GAM MCP Server environment.

WHY IT NEEDS A POLICY

Why reapply_anyone_permissions needs a policy

The tool name 'reapply_anyone_permissions' suggests it modifies or resets sharing permissions, which is a reversible write operation. While the empty description reduces confidence, the GAM MCP Server context (administrative actions on Google Workspace including Drive and permissions management) and the presence of multiple audit_*_permissions sibling tools indicate this performs permission adjustments.

From the tool's definition Tool name is 'reapply_anyone_permissions' indicating it modifies access permissions; sibling tools audit permissions suggesting this server manages Google Workspace access controls; description is empty but context from related audit tools and server purpose…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reapply_anyone_permissions Rate-limited

reapply_anyone_permissions 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": {
    "reapply_anyone_permissions": {
      "limits": [
        {
          "counter": "reapply_anyone_permissions_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 GAM MCP Server, so you can run agents against it safely.

FAQ

Questions about reapply_anyone_permissions

What does the reapply_anyone_permissions tool do? +

reapply_anyone_permissions. It is categorised as a Write tool in the GAM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reapply_anyone_permissions? +

Register the GAM MCP Server MCP server in PolicyLayer and add a rule for reapply_anyone_permissions: 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 GAM MCP Server. Nothing to install.

What risk level is reapply_anyone_permissions? +

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

Can I rate-limit reapply_anyone_permissions? +

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

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

reapply_anyone_permissions is provided by the GAM MCP Server MCP server (ktibbs9417/gamcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.