omarchy_webapp_handler_zoom
Open Zoom web meetings from browser protocol links [group:webapp] Args: [url]
This record as markdown: /tools/omarchy-mcp/omarchy-webapp-handler-zoom.md
What omarchy_webapp_handler_zoom does on Omarchy-MCP
AI agents invoke omarchy_webapp_handler_zoom to trigger actions in Omarchy-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why omarchy_webapp_handler_zoom is rated High
Triggers external application launch and network connection to meeting service.
From the tool's definition Open Zoom web meetings from browser protocol links
Attacks that exploit this kind of access
The rule that runs omarchy_webapp_handler_zoom safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Omarchy-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For omarchy_webapp_handler_zoom, this is the rule to start with:
omarchy_webapp_handler_zoom stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every omarchy_webapp_handler_zoom call is checked against it from then on.
Questions about omarchy_webapp_handler_zoom
Open Zoom web meetings from browser protocol links [group:webapp] Args: [url]. It is categorised as a Execute tool in the Omarchy-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Omarchy MCP server in PolicyLayer and add a rule for omarchy_webapp_handler_zoom: 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 Omarchy-MCP. Nothing to install.
omarchy_webapp_handler_zoom is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the omarchy_webapp_handler_zoom 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 omarchy_webapp_handler_zoom. 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.
omarchy_webapp_handler_zoom is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Omarchy, and thousands of servers like it.
Across the catalogue