Move a slide from one position to another in a Keynote presentation.
AI agents use keynote.reorder_slides to create or update resources in Orchard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Orchard environment.
Reordering slides modifies the structure of a Keynote presentation by changing slide positions. This is a reversible write operation (slides can be moved back), but misuse could disrupt presentation order. No data is deleted or executed, making Write the appropriate category.
From the tool's definition Move a slide from one position to another in a Keynote presentation
Documented attack patterns abuse exactly the kind of access keynote.reorder_slides gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orchard, and nothing reaches the server without passing your rules. This is the rule we recommend for keynote.reorder_slides:
{
"version": "1",
"default": "deny",
"tools": {
"keynote.reorder_slides": {
"limits": [
{
"counter": "keynote.reorder_slides_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}keynote.reorder_slides stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Move a slide from one position to another in a Keynote presentation. It is categorised as a Write tool in the Orchard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Orchard MCP server in PolicyLayer and add a rule for keynote.reorder_slides: 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 Orchard. Nothing to install.
keynote.reorder_slides 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 keynote.reorder_slides 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 keynote.reorder_slides. 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.
keynote.reorder_slides is provided by the Orchard MCP server (l22-io/orchard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orchard, 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.
65 Orchard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.