AI agents use manage_slide to create or update resources in Powerpoint — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Powerpoint environment.
Based on the server's purpose (editing presentations) and sibling tools that perform creation/modification operations, 'manage_slide' most likely creates, modifies, or reorders slides—reversible write operations. The presence of destructive tools like 'delete_shape' on the same server suggests 'manage_slide' is distinct and therefore non-destructive.
From the tool's definition Tool name 'manage_slide' is part of a PowerPoint editing server alongside tools like 'add_chart', 'add_image', 'add_shape', 'delete_shape', and 'find_and_replace'. The context indicates this server is designed to 'Create and edit PowerPoint presentations'.
Documented attack patterns abuse exactly the kind of access manage_slide gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Powerpoint, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_slide:
{
"version": "1",
"default": "deny",
"tools": {
"manage_slide": {
"limits": [
{
"counter": "manage_slide_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_slide stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
manage_slide. It is categorised as a Write tool in the Powerpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Powerpoint MCP server in PolicyLayer and add a rule for manage_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 Powerpoint. Nothing to install.
manage_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 manage_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 manage_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.
manage_slide is provided by the Powerpoint MCP server (juanocampo400/powerpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Powerpoint, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Powerpoint tools catalogued and risk-classified — across an index of 43,000+ MCP servers.