Critical Risk →

keynote_close_presentation

Close a Keynote presentation

How to control keynote_close_presentation ↓

What keynote_close_presentation does on Iwork

AI agents call keynote_close_presentation 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.

Critical Risk

Why keynote_close_presentation needs a policy

Closing a presentation without saving can result in irreversible loss of unsaved changes. Depending on the implementation (e.g., closing without prompting to save), this could permanently discard work. Since the effect may be irreversible (data loss), Destructive is the most appropriate category, though it's not a delete/drop operation in the traditional sense.

From the tool's definition Close a Keynote presentation

Documented attack patterns abuse exactly the kind of access keynote_close_presentation gives an agent:

How to control keynote_close_presentation

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_close_presentation:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "keynote_close_presentation"
  ]
}

keynote_close_presentation disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Iwork — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about keynote_close_presentation

What does the keynote_close_presentation tool do? +

Close a Keynote 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.

How do I enforce a policy on keynote_close_presentation? +

Register the Iwork MCP server in PolicyLayer and add a rule for keynote_close_presentation: 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.

What risk level is keynote_close_presentation? +

keynote_close_presentation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit keynote_close_presentation? +

Yes. Add a rate_limit block to the keynote_close_presentation 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.

How do I block keynote_close_presentation completely? +

Set action: deny in the PolicyLayer policy for keynote_close_presentation. 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.

What MCP server provides keynote_close_presentation? +

keynote_close_presentation 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.

Enforce policy on every Iwork tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.