Get Zoom meeting details. Args: meeting_id: Zoom meeting ID.
AI agents call zoom_get_meeting to retrieve information from autoMate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves meeting information from Zoom using a meeting ID parameter. Retrieval and query operations that do not modify data, execute code, or cause irreversible changes are classified as Read.
From the tool's definition Tool name is 'zoom_get_meeting' and description states 'Get Zoom meeting details' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access zoom_get_meeting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for zoom_get_meeting:
{
"version": "1",
"default": "deny",
"tools": {
"zoom_get_meeting": {}
}
}zoom_get_meeting 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.
Get Zoom meeting details. Args: meeting_id: Zoom meeting ID. It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.
Register the autoMate 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 autoMate. 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 autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.