Export a Keynote presentation to PDF, PowerPoint, PNG, or JPEG.
AI agents invoke keynote.export to trigger actions in Orchard. 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 (exporting/converting a file) that produces new output files on the filesystem. It is not a pure read (it creates new files) nor destructive (it doesn't delete the source), so Execute is the most appropriate category. Misuse could lead to unintended file creation or data exfiltration via export.
From the tool's definition Export a Keynote presentation to PDF, PowerPoint, PNG, or JPEG
Documented attack patterns abuse exactly the kind of access keynote.export 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.export:
{
"version": "1",
"default": "deny",
"tools": {
"keynote.export": {
"limits": [
{
"counter": "keynote.export_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} keynote.export 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.
Free to start. No card required.
Export a Keynote presentation to PDF, PowerPoint, PNG, or JPEG. It is categorised as a Execute tool in the Orchard MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Orchard MCP server in PolicyLayer and add a rule for keynote.export: 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.export 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 keynote.export 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.export. 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.export 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.