Delete a slide from the presentation.
AI agents call keynote_delete_slide 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.
Deleting a slide is a destructive operation that permanently removes content from the presentation and cannot be undone through the tool itself. While the user may have backups, the action is irreversible at the API level. High severity due to potential loss of significant presentation work. Classified as Destructive rather than Write because deletion is not reversible through normal tool operations.
From the tool's definition Tool name 'keynote_delete_slide' and description 'Delete a slide from the presentation' directly indicate irreversible deletion of presentation content.
Attacks that exploit this kind of access
Delete a slide from the presentation. 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_slide: 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_slide 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_slide 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_slide. 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_slide 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 →