Jumps to a specific slide during an active Keynote slideshow.
AI agents invoke go_to_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.
This tool triggers an external operation (controlling an active Keynote slideshow by navigating to a specific slide). It doesn't read, write, or destroy data, but it executes a UI/application action that affects the state of a running presentation.
From the tool's definition Jumps to a specific slide during an active Keynote slideshow
Attacks that exploit this kind of access
Jumps to a specific slide 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.
Register the Keynote MCP Server MCP server in PolicyLayer and add a rule for go_to_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.
go_to_slide is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the go_to_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.
Set action: deny in the PolicyLayer policy for go_to_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.
go_to_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →