High Risk →

keynote_start_slideshow

Start playing the presentation slideshow

How to control keynote_start_slideshow ↓

What keynote_start_slideshow does on Iwork

AI agents invoke keynote_start_slideshow 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_start_slideshow needs a policy

This tool executes a command that initiates a presentation slideshow, which is an observable external action. While not destructive or financially harmful, it qualifies as Execute because it triggers an operation whose effects depend on arguments (the presentation being played) and state.

From the tool's definition Tool description states 'Start playing the presentation slideshow' — this triggers an external operation (slideshow playback) whose effects depend on presentation state and content.

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

How to control keynote_start_slideshow

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

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

keynote_start_slideshow 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_start_slideshow

What does the keynote_start_slideshow tool do? +

Start playing the presentation slideshow. 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_start_slideshow? +

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

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

Can I rate-limit keynote_start_slideshow? +

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

Set action: deny in the PolicyLayer policy for keynote_start_slideshow. 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_start_slideshow? +

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