Edit an existing slide
AI agents use keynote.edit_slide 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.
The tool modifies presentation content reversibly by editing a slide. This is a Write operation—it changes data but does not delete or irreversibly destroy it. Severity is medium because misuse could corrupt or deface a user's presentation, but the changes are typically undoable via undo/version history in most applications.
From the tool's definition Tool name 'edit_slide' and description 'Edit an existing slide' indicate modification of existing data (a Keynote presentation slide).
Documented attack patterns abuse exactly the kind of access keynote.edit_slide 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.edit_slide:
{
"version": "1",
"default": "deny",
"tools": {
"keynote.edit_slide": {
"limits": [
{
"counter": "keynote.edit_slide_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}keynote.edit_slide 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.
Edit an existing slide. 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.edit_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 Orchard. Nothing to install.
keynote.edit_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 keynote.edit_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 keynote.edit_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.
keynote.edit_slide 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.