This record as markdown: /tools/sagemcp-sagemcp/zoom-get-meeting.md
What zoom_get_meeting does on Sage MCP
AI agents call zoom_get_meeting to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why zoom_get_meeting is rated Low
This tool retrieves meeting information from Zoom by querying an existing meeting ID. It performs a read-only lookup operation with no capability to modify, create, delete, or execute any actions. The meeting details returned may contain sensitive information (participant lists, recording status, etc.), but the tool itself is purely informational.
From the tool's definition Tool name 'zoom_get_meeting' and description 'Get details of a specific meeting by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs zoom_get_meeting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zoom_get_meeting, this is the rule to start with:
zoom_get_meeting 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 Sage MCP, apply this rule, and every zoom_get_meeting call is checked against it from then on.
Questions about zoom_get_meeting
Get details of a specific meeting by ID. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for zoom_get_meeting: 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 Sage MCP. Nothing to install.
zoom_get_meeting 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 zoom_get_meeting 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 zoom_get_meeting. 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.
zoom_get_meeting is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue