add_slide
AI agents use add_slide to create or update resources in Cross-Platform PowerPoint MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cross-Platform PowerPoint MCP Server environment.
Adding a slide creates new content within a presentation file in a reversible manner—slides can be deleted or modified later. This is a Write operation rather than Read (no data retrieval), Execute (no arbitrary command execution), Destructive (reversible), or Financial (no financial impact).
From the tool's definition Tool name 'add_slide' and sibling tools like 'create_presentation', 'open_presentation', 'save_presentation', and 'add_text_box' indicate this server performs presentation creation and modification.
Attacks that exploit this kind of access
add_slide. It is categorised as a Write tool in the Cross-Platform PowerPoint MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cross-Platform PowerPoint MCP Server MCP server in PolicyLayer and add a rule for add_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 Cross-Platform PowerPoint MCP Server. Nothing to install.
add_slide 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 add_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 add_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.
add_slide is provided by the Cross-Platform PowerPoint MCP Server MCP server (vancealexander/powerpoint_mcp_crossplatform). 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 →