stop_slideshow · Keynote MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_slideshow does on Keynote MCP Server

AI agents invoke stop_slideshow to trigger actions in Keynote MCP Server. 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.

WHY IT NEEDS A POLICY

Why stop_slideshow needs a policy

The tool executes a command that controls an external application (Apple Keynote) and changes its operational state. While the action itself is reversible (a user can restart the slideshow), it represents execution of an operation with side effects on a running process.

From the tool's definition Tool description states it 'Stops the currently running Keynote slideshow.' This is a command that triggers an external operation (halting a presentation) whose effects depend on the application state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_slideshow Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_slideshow": {
      "limits": [
        {
          "counter": "stop_slideshow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Keynote MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_slideshow

What does the stop_slideshow tool do? +

Stops the currently running Keynote slideshow. It is categorised as a Execute tool in the Keynote MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_slideshow? +

Register the Keynote MCP Server MCP server in PolicyLayer and add a rule for stop_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 Keynote MCP Server. Nothing to install.

What risk level is stop_slideshow? +

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

Can I rate-limit stop_slideshow? +

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

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

stop_slideshow is provided by the Keynote MCP Server MCP server (superdwayne/keynotemp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.