GOOGLESUPER_CREATE_MEET
Creates a new Google Meet space, optionally configuring its access type and entry point access controls.
This record as markdown: /tools/googlesuper/googlesuper-create-meet.md
What GOOGLESUPER_CREATE_MEET does on Google Super
AI agents use GOOGLESUPER_CREATE_MEET to create or update resources in Google Super, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Super environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
access_type | string | — | Access control level for the meeting space. |
entry_point_access | string | — | Access control for meeting entry points. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_CREATE_MEET is rated Medium
This tool creates a new Google Meet (a reversible resource creation). While it can configure access controls, the core function is to instantiate a new meeting space, making it a Write operation rather than Execute.
From the tool's definition Tool description states it 'Creates a new Google Meet space' which is a resource creation operation that modifies state by adding a new calendar/communication object.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_CREATE_MEET safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_CREATE_MEET, this is the rule to start with:
GOOGLESUPER_CREATE_MEET 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_CREATE_MEET call is checked against it from then on.
Questions about GOOGLESUPER_CREATE_MEET
Creates a new Google Meet space, optionally configuring its access type and entry point access controls. It is categorised as a Write tool in the Google Super MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
GOOGLESUPER_CREATE_MEET accepts 2 parameters: access_type, entry_point_access. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_CREATE_MEET: 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 Google Super. Nothing to install.
GOOGLESUPER_CREATE_MEET 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 GOOGLESUPER_CREATE_MEET 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 GOOGLESUPER_CREATE_MEET. 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.
GOOGLESUPER_CREATE_MEET is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
This server
Across the catalogue