Mark a slide as skipped (hidden) or unskipped
AI agents use keynote_skip_slide 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 modifies slide properties (visibility/skip status) but does not delete content, execute arbitrary code, or cause irreversible changes. The action is fully reversible by unmarking the slide as skipped. This constitutes a Write operation with low severity since misuse would only temporarily hide slides in a presentation without data loss or external effects.
From the tool's definition Tool description states: 'Mark a slide as skipped (hidden) or unskipped' — this is a reversible modification of presentation metadata (slide visibility state).
Documented attack patterns abuse exactly the kind of access keynote_skip_slide 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_skip_slide:
{
"version": "1",
"default": "deny",
"tools": {
"keynote_skip_slide": {
"limits": [
{
"counter": "keynote_skip_slide_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}keynote_skip_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.
Mark a slide as skipped (hidden) or unskipped. 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_skip_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 Iwork. Nothing to install.
keynote_skip_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_skip_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_skip_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_skip_slide 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.