Set a transition effect on a slide
AI agents use keynote_set_transition to create or update resources in Iwork — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iwork environment.
This tool creates or modifies presentation content (transition effects) reversibly. It does not execute arbitrary code, delete data, move financial assets, or perform read-only queries. Transition effects are standard slide properties in presentation software and changes are easily editable, meeting the criteria for Write category with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate it modifies slide properties non-destructively: 'Set a transition effect on a slide' — updates presentation metadata that can be changed or removed.
Documented attack patterns abuse exactly the kind of access keynote_set_transition gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iwork, and nothing reaches the server without passing your rules. This is the rule we recommend for keynote_set_transition:
{
"version": "1",
"default": "deny",
"tools": {
"keynote_set_transition": {
"limits": [
{
"counter": "keynote_set_transition_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}keynote_set_transition 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.
Set a transition effect on a slide. It is categorised as a Write tool in the Iwork MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iwork MCP server in PolicyLayer and add a rule for keynote_set_transition: 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 Iwork. Nothing to install.
keynote_set_transition 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_set_transition 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_set_transition. 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_set_transition is provided by the Iwork MCP server (reichenbach/iwork_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iwork, 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.
114 Iwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.