Move and/or resize an item (shape, image, or textItem) on a slide by type and index
AI agents use keynote_position_item 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 presentation elements (position and size of shapes, images, or text items) but does not delete content or execute arbitrary code. The changes are reversible—items can be repositioned again. While it alters a document, it falls under Write rather than Execute because it performs a direct, bounded data modification rather than executing external operations or running arbitrary scripts.
From the tool's definition Tool description states it can "Move and/or resize an item" on a slide, which are reversible modifications to presentation content.
Documented attack patterns abuse exactly the kind of access keynote_position_item 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_position_item:
{
"version": "1",
"default": "deny",
"tools": {
"keynote_position_item": {
"limits": [
{
"counter": "keynote_position_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}keynote_position_item 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 and/or resize an item (shape, image, or textItem) on a slide by type and index. 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_position_item: 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_position_item 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_position_item 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_position_item. 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_position_item 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.