Moves a slide from one position to another in the frontmost presentation.
AI agents use move_slide to create or update resources in Keynote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keynote MCP Server environment.
Moving a slide reorders presentation content but does not create, delete, or destroy data—it is reversible. This fits the Write category (modifies data reversibly). Severity is medium because misuse could disrupt presentation structure and content organization, but the effect is limited to slide ordering within a single presentation and can be undone.
From the tool's definition The tool description states it "Moves a slide from one position to another in the frontmost presentation," which modifies the structure and order of presentation content.
Attacks that exploit this kind of access
Moves a slide from one position to another in the frontmost presentation. It is categorised as a Write tool in the Keynote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keynote MCP Server MCP server in PolicyLayer and add a rule for move_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.
move_slide is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_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 move_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.
move_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 →