create_collaborative_inbox_group
AI agents use create_collaborative_inbox_group 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.
Creating a Google Workspace group is a Write operation—it instantiates a new resource that can be modified or deleted later. While the tool has organizational impact (blast radius includes group membership and associated permissions), it is reversible, so it does not rise to Destructive or Execute severity.
From the tool's definition Tool name 'create_collaborative_inbox_group' indicates creation of a group resource. Server context shows GAM7 administrative functions for Google Workspace, which manages users and groups.
Attacks that exploit this kind of access
create_collaborative_inbox_group. 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 create_collaborative_inbox_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 GAM MCP Server. Nothing to install.
create_collaborative_inbox_group 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 create_collaborative_inbox_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 create_collaborative_inbox_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.
create_collaborative_inbox_group 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 →