Delete a slide from the presentation
AI agents call delete_slide to permanently remove resources in ContextForge MCP Gateway — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on presentation data. Once a slide is deleted, the action cannot be undone through the tool itself, making this a destructive operation. The high severity reflects the potential for significant data loss if an AI agent misuses this tool by deleting multiple slides or critical presentation content without proper authorization or safeguards.
From the tool's definition Tool name 'delete_slide' and description 'Delete a slide from the presentation' explicitly indicate irreversible removal of presentation content.
Attacks that exploit this kind of access
Delete a slide from the presentation. It is categorised as a Destructive tool in the ContextForge MCP Gateway MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for delete_slide: 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.
delete_slide is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_slide 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 delete_slide. 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.
delete_slide 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 →