Set the title of a slide
AI agents use set_slide_title to create or update resources in ContextForge MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextForge MCP Gateway environment.
This tool modifies slide metadata (title) in a reversible manner. It does not execute code, delete data, or trigger external operations. The sibling tools (add_content, add_heading, add_section, etc.) confirm this is a document/presentation editing context where Write operations are expected. The blast radius is minimal—a slide title can be easily corrected.
From the tool's definition Tool name 'set_slide_title' and description 'Set the title of a slide' indicate a modification operation that updates slide content. The verb 'set' implies creating or modifying data.
Attacks that exploit this kind of access
Set the title of a slide. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ContextForge MCP Gateway 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 ContextForge MCP Gateway. 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 ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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 →