AI agents use create_meeting to create or update resources in Zoom MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zoom MCP Server environment.
Creating a meeting is a reversible write operation - the meeting can be subsequently modified or deleted. It has moderate severity because unauthorized meeting creation could disrupt users, consume resources, or enable spam/phishing campaigns through meeting invitations, but the impact is limited in scope compared to destructive or financial operations.
From the tool's definition Tool name is 'create_meeting' and description states 'Create a meeting'. This is a create operation that generates new data (a meeting resource) within the Zoom platform.
Documented attack patterns abuse exactly the kind of access create_meeting 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 create_meeting:
{
"version": "1",
"default": "deny",
"tools": {
"create_meeting": {
"limits": [
{
"counter": "create_meeting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_meeting stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a meeting. It is categorised as a Write tool in the Zoom MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zoom MCP Server MCP server in PolicyLayer and add a rule for create_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 Zoom MCP Server. Nothing to install.
create_meeting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_meeting 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.