GOOGLESUPER_LIST_CONFERENCE_RECORDS

Tool to list conference records. Use when you need to retrieve a list of past conferences, optionally filtering them by criteria like meeting code, space name, or time range.

SERVERGoogle Super SOURCEgooglesuper

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/googlesuper/googlesuper-list-conference-records.md

WHAT IT DOES

What GOOGLESUPER_LIST_CONFERENCE_RECORDS does on Google Super

AI agents call GOOGLESUPER_LIST_CONFERENCE_RECORDS 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
`filter`	string	—	Optional. User specified filtering condition in EBNF format. Filterable fields: `space.meeting_code`, `space.name`, `start_time`, `end_time`. Examples: `space.n
`page_size`	integer	—	Maximum number of conference records to return. The service might return fewer than this value. If unspecified, at most 25 conference records are returned. The
`page_token`	string	—	Page token returned from previous List Call.

Parameters from the server's own tool schema.

RISK

Why GOOGLESUPER_LIST_CONFERENCE_RECORDS is rated Low

This tool performs a read-only operation that retrieves and filters existing conference records without any side effects. It does not create, modify, delete, or execute any operations. The blast radius is minimal—exposure would allow an AI agent to view conference metadata but not alter any data or trigger actions.

From the tool's definition Tool description states it 'retrieve[s] a list of past conferences' with optional filtering by meeting code, space name, or time range. No modification, deletion, or execution keywords are present.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GOOGLESUPER_LIST_CONFERENCE_RECORDS 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_LIST_CONFERENCE_RECORDS, this is the rule to start with:

GOOGLESUPER_LIST_CONFERENCE_RECORDS Allowed

GOOGLESUPER_LIST_CONFERENCE_RECORDS is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "GOOGLESUPER_LIST_CONFERENCE_RECORDS": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_LIST_CONFERENCE_RECORDS call is checked against it from then on.

FAQ

Questions about GOOGLESUPER_LIST_CONFERENCE_RECORDS

What does the GOOGLESUPER_LIST_CONFERENCE_RECORDS tool do? +

Tool to list conference records. Use when you need to retrieve a list of past conferences, optionally filtering them by criteria like meeting code, space name, or time range. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.

What parameters does GOOGLESUPER_LIST_CONFERENCE_RECORDS accept? +

GOOGLESUPER_LIST_CONFERENCE_RECORDS accepts 3 parameters: filter, page_size, page_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_LIST_CONFERENCE_RECORDS? +

Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_LIST_CONFERENCE_RECORDS: 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.

What risk level is GOOGLESUPER_LIST_CONFERENCE_RECORDS? +

GOOGLESUPER_LIST_CONFERENCE_RECORDS is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit GOOGLESUPER_LIST_CONFERENCE_RECORDS? +

Yes. Add a rate_limit block to the GOOGLESUPER_LIST_CONFERENCE_RECORDS 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.

How do I block GOOGLESUPER_LIST_CONFERENCE_RECORDS completely? +

Set action: deny in the PolicyLayer policy for GOOGLESUPER_LIST_CONFERENCE_RECORDS. 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.

What MCP server provides GOOGLESUPER_LIST_CONFERENCE_RECORDS? +

GOOGLESUPER_LIST_CONFERENCE_RECORDS 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.

KEEP EXPLORING

More on Google Super, and thousands of servers like it.

This server

All 200 Google Super tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →