High Risk →

keynote_open_presentation

Open a .key file from disk

How to control keynote_open_presentation ↓

What keynote_open_presentation does on Iwork

AI agents invoke keynote_open_presentation to trigger actions in Iwork. 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.

High Risk

Why keynote_open_presentation needs a policy

Opening a file from disk triggers an external application operation (launching/activating Keynote via JavaScript for Automation), which is more than a passive read — it causes side effects in the OS and application state. It does not merely retrieve data but executes an automation action that opens a file in an external app.

From the tool's definition Open a .key file from disk

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

How to control keynote_open_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_open_presentation:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "keynote_open_presentation": {
      "limits": [
        {
          "counter": "keynote_open_presentation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

keynote_open_presentation stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about keynote_open_presentation

What does the keynote_open_presentation tool do? +

Open a .key file from disk. It is categorised as a Execute tool in the Iwork MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on keynote_open_presentation? +

Register the Iwork MCP server in PolicyLayer and add a rule for keynote_open_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_open_presentation? +

keynote_open_presentation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit keynote_open_presentation? +

Yes. Add a rate_limit block to the keynote_open_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_open_presentation completely? +

Set action: deny in the PolicyLayer policy for keynote_open_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_open_presentation? +

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