Sets the title text of a slide
AI agents use set_slide_title 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 modifies presentation content (the slide title) in a way that is reversible—the title can be changed again or restored. It does not delete data, execute arbitrary code, move money, or trigger external operations. It clearly fits the Write category as it creates or modifies data reversibly.
From the tool's definition Tool name 'set_slide_title' and description 'Sets the title text of a slide' indicate it modifies existing slide content by changing the title, a reversible operation that creates or modifies data within a presentation.
Attacks that exploit this kind of access
Sets the title 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_title: 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_title 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_title 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_title. 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_title 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 →