Delete an element from a slide. Use with care — this cannot be undone via the MCP. Keynote undo (Cmd+Z) still works in the app.
AI agents call keynote_delete_element to permanently remove resources in Keynote — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes slide elements from Keynote presentations. While Keynote's native undo may recover changes, the MCP itself cannot undo deletions, making this a destructive operation. The explicit warning and inability to reverse via the protocol interface confirm destructive classification.
From the tool's definition 'Delete an element from a slide. Use with care — this cannot be undone via the MCP' indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete an element from a slide. Use with care — this cannot be undone via the MCP. Keynote undo (Cmd+Z) still works in the app. It is categorised as a Destructive tool in the Keynote MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Keynote MCP server in PolicyLayer and add a rule for keynote_delete_element: 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 Keynote. Nothing to install.
keynote_delete_element is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the keynote_delete_element 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 keynote_delete_element. 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.
keynote_delete_element is provided by the Keynote MCP server (tszaks/keynote-mcp). 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 →