next_slide · Keynote MCP Server MCP: Risk & Policy

WHAT IT DOES

What next_slide does on Keynote MCP Server

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

This is Execute rather than Read because it performs an action that changes the state of an external system (advancing a live presentation) rather than passively retrieving information.

From the tool's definition Tool advances to the next slide during an active slideshow—this triggers a state change in an external application (Keynote) based on the agent's action. The description says 'Advances to the next slide' which is an external operation with observable effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

next_slide Rate-limited

next_slide 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": {
    "next_slide": {
      "limits": [
        {
          "counter": "next_slide_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 next_slide

What does the next_slide tool do? +

Advances to the next slide or build during an active 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 next_slide? +

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

What risk level is next_slide? +

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

Can I rate-limit next_slide? +

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

How do I block next_slide completely? +

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

What MCP server provides next_slide? +

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