AI agents call keynote_delete_slide to permanently remove resources in Iwork — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a slide removes content that cannot be recovered without undo/backup mechanisms external to this tool. This is a destructive operation with high blast radius if an AI agent mistakenly deletes critical slides from a presentation. The severity is high (not critical) because the impact is scoped to a single presentation file, though the data loss is permanent at the tool level.
From the tool's definition Tool name is 'keynote_delete_slide' and description states 'Delete a slide from the presentation' — the word 'delete' is explicit. Deletion of slides is irreversible content destruction.
Documented attack patterns abuse exactly the kind of access keynote_delete_slide gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iwork, and nothing reaches the server without passing your rules. This is the rule we recommend for keynote_delete_slide:
{
"version": "1",
"default": "deny",
"hide": [
"keynote_delete_slide"
]
}keynote_delete_slide disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a slide from the presentation. It is categorised as a Destructive tool in the Iwork MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Iwork 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 Iwork. 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 Iwork MCP server (reichenbach/iwork_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iwork, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
114 Iwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.