Sets the body text of a slide
AI agents use set_slide_body 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.
The tool modifies slide content (body text) within a presentation, which is a reversible change. While presentations can be important documents, the modification is not destructive (content can be edited or undone), not financial, and does not execute arbitrary code. It fits the Write category as a content modification operation.
From the tool's definition Tool name 'set_slide_body' combined with description 'Sets the body text of a slide' indicates creation or modification of presentation content. This is a reversible write operation on slide content.
Attacks that exploit this kind of access
Sets the body text of a slide. 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 set_slide_body: 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.
set_slide_body 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 set_slide_body 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 set_slide_body. 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.
set_slide_body 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 →