Replaces an existing image on a slide with a new image file
AI agents use replace_image to create or update resources in Keynote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keynote MCP Server environment.
This tool creates or modifies presentation data in a reversible manner by substituting one image for another on a slide. It does not delete data permanently, execute arbitrary code, or move financial resources. The medium severity reflects that misuse could corrupt a presentation's visual content, but the effect is limited to a single asset and can be undone.
From the tool's definition Tool name 'replace_image' and description 'Replaces an existing image on a slide with a new image file' indicate modification of presentation content.
Attacks that exploit this kind of access
Replaces an existing image on a slide with a new image file. It is categorised as a Write tool in the Keynote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keynote MCP Server MCP server in PolicyLayer and add a rule for replace_image: 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 MCP Server. Nothing to install.
replace_image 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 replace_image 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 replace_image. 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.
replace_image is provided by the Keynote MCP Server MCP server (superdwayne/keynotemp). 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 →