GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_MEET
Get conference record
This record as markdown: /tools/googlesuper/googlesuper-get-conference-record-for-meet.md
What GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_MEET does on Google Super
AI agents call GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_MEET to retrieve information from Google Super without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end_time | string | — | The end time of the meeting in RFC3339 timestamp format (e.g., '2024-01-15T11:00:00Z' or '2024-01-15T11:00:00+00:00'). |
space_name | string | — | The resource name of the Google Meet space in the format 'spaces/{space_id}'. Example: 'spaces/mV63iV9-KxoB'. |
start_time | string | — | The start time of the meeting in RFC3339 timestamp format (e.g., '2024-01-15T10:00:00Z' or '2024-01-15T10:00:00+00:00'). |
meeting_code | string | — | The meeting code of the Google Meet space. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_MEET is rated Low
This tool queries and retrieves conference records from Google Meet, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal — an attacker could view conference records they may not have authorization for, but cannot alter data or trigger external operations.
From the tool's definition Tool name contains 'GET' and description states 'Get conference record' — retrieves existing data without modification, deletion, or execution of actions.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_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_GET_CONFERENCE_RECORD_FOR_MEET, this is the rule to start with:
GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_MEET is read-only, so it stays allowed. 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_GET_CONFERENCE_RECORD_FOR_MEET call is checked against it from then on.
Questions about GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_MEET
Get conference record. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_MEET accepts 4 parameters: end_time, space_name, start_time, meeting_code. 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_GET_CONFERENCE_RECORD_FOR_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_GET_CONFERENCE_RECORD_FOR_MEET is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the GOOGLESUPER_GET_CONFERENCE_RECORD_FOR_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_GET_CONFERENCE_RECORD_FOR_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_GET_CONFERENCE_RECORD_FOR_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