reapply_domain_permissions
AI agents use reapply_domain_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.
The tool performs permission reconfiguration across a domain scope, which modifies access controls on potentially many resources. This is a Write operation (reversible configuration change) rather than Destructive. Severity is high due to the broad blast radius—domain-wide permission changes can affect multiple users and resources.
From the tool's definition Tool name 'reapply_domain_permissions' and server context (GAM7 Google Workspace administration). The name indicates modifying permission settings at a domain level. No description provided, limiting specificity.
Attacks that exploit this kind of access
reapply_domain_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.
Register the GAM MCP Server MCP server in PolicyLayer and add a rule for reapply_domain_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.
reapply_domain_permissions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reapply_domain_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.
Set action: deny in the PolicyLayer policy for reapply_domain_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.
reapply_domain_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.
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 →