AI agents call list_meetings to retrieve information from Zoom MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries scheduled meeting information from Zoom without creating, modifying, deleting, or executing any operations. It is a passive read operation with minimal security risk, as it only lists existing meetings that the authenticated user has access to. The low severity reflects that unauthorized listing could expose meeting schedules but cannot directly harm systems or data.
From the tool's definition Tool name 'list_meetings' and description 'List scheduled meetings' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_meetings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zoom MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_meetings:
{
"version": "1",
"default": "deny",
"tools": {
"list_meetings": {}
}
}list_meetings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List scheduled meetings. It is categorised as a Read tool in the Zoom MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zoom MCP Server MCP server in PolicyLayer and add a rule for list_meetings: 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 Zoom MCP Server. Nothing to install.
list_meetings 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 list_meetings 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 list_meetings. 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.
list_meetings is provided by the Zoom MCP Server MCP server (javaprogrammerlb/zoom-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zoom MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Zoom MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.