Open Keynote on macOS and create a new document.
AI agents invoke mac_open_keynote to trigger actions in Math MCP Server for MacOS. 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.
This tool triggers an external application (Keynote) on the host OS and creates a new document. It involves executing a system-level operation (launching an application) and performing a write action (creating a document). Since it runs an external process on the OS, Execute is the most appropriate category. Severity is medium as misuse could spawn unwanted application instances or create files on the user's system.
From the tool's definition Open Keynote on macOS and create a new document
Attacks that exploit this kind of access
Open Keynote on macOS and create a new document. It is categorised as a Execute tool in the Math MCP Server for MacOS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Math MCP Server for MacOS MCP server in PolicyLayer and add a rule for mac_open_keynote: 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 Math MCP Server for MacOS. Nothing to install.
mac_open_keynote 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 mac_open_keynote 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 mac_open_keynote. 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.
mac_open_keynote is provided by the Math MCP Server for MacOS MCP server (rohinigaonkar/mcp-math-macos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →