AI agents use zoom_create_meeting to create or update resources in autoMate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your autoMate environment.
Creating a meeting is a reversible Write operation—meetings can be cancelled or modified. This is not a Destructive action (meetings persist and can be deleted), not Financial (no money involved), and not Execute (no arbitrary code execution). The absence of a description lowers confidence slightly, but the tool name clearly indicates creation of a new resource.
From the tool's definition Tool name 'zoom_create_meeting' indicates creation of a new meeting resource. No description provided, but naming convention parallels sibling tools like 'airtable_create_record' and 'asana_create_task' which are Write operations.
Documented attack patterns abuse exactly the kind of access zoom_create_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_create_meeting:
{
"version": "1",
"default": "deny",
"tools": {
"zoom_create_meeting": {
"limits": [
{
"counter": "zoom_create_meeting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}zoom_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.
zoom_create_meeting. It is categorised as a Write tool in the autoMate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the autoMate MCP server in PolicyLayer and add a rule for zoom_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 autoMate. Nothing to install.
zoom_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 zoom_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 zoom_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.
zoom_create_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.