GOOGLESUPER_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID
Retrieves recordings from Google Meet for a given conference record ID.
This record as markdown: /tools/googlesuper/googlesuper-get-recordings-by-conference-record-id.md
What GOOGLESUPER_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID does on Google Super
AI agents call GOOGLESUPER_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID 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 |
|---|---|---|---|
conferenceRecord_id | string | — | Unique identifier for the conference record. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID is rated Low
This tool performs a data retrieval operation that queries and returns Google Meet recordings based on a conference record ID. The verb 'retrieves' and the GET prefix indicate no modification, deletion, or execution of code. While recordings could contain sensitive information, the tool itself is a passive read operation with no side effects.
From the tool's definition Tool name contains 'GET_RECORDINGS_BY' and description states 'Retrieves recordings', which indicates a read-only data retrieval operation.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID 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_RECORDINGS_BY_CONFERENCE_RECORD_ID, this is the rule to start with:
GOOGLESUPER_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID 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_RECORDINGS_BY_CONFERENCE_RECORD_ID call is checked against it from then on.
Questions about GOOGLESUPER_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID
Retrieves recordings from Google Meet for a given conference record ID. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_GET_RECORDINGS_BY_CONFERENCE_RECORD_ID accepts 1 parameter: conferenceRecord_id. 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_RECORDINGS_BY_CONFERENCE_RECORD_ID: 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_RECORDINGS_BY_CONFERENCE_RECORD_ID 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_RECORDINGS_BY_CONFERENCE_RECORD_ID 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_RECORDINGS_BY_CONFERENCE_RECORD_ID. 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_RECORDINGS_BY_CONFERENCE_RECORD_ID 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