AI agents use keynote_set_element_position to create or update resources in Keynote — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keynote environment.
This tool modifies slide layout by repositioning elements, which is a reversible change to presentation structure. While it alters the presentation, it does not delete content, execute code, or create permanent effects. It falls under Write category as it updates object properties.
From the tool's definition Tool name 'keynote_set_element_position' and description 'Move an element to a new position on the slide' indicate modification of existing slide element properties without deletion or irreversible data loss.
Attacks that exploit this kind of access
Move an element to a new position on the slide. Coordinates are in points from the top-left corner. Keynote standard slide is 1920×1080 pts. It is categorised as a Write tool in the Keynote MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keynote MCP server in PolicyLayer and add a rule for keynote_set_element_position: 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 Keynote. Nothing to install.
keynote_set_element_position 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_element_position 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_element_position. 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_element_position is provided by the Keynote MCP server (tszaks/keynote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →