AI agents use connect_shapes to create or update resources in PowerPoint MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PowerPoint MCP Server environment.
The tool performs a reversible modification to presentation content by establishing a visual connection between existing shapes. This is a write operation that creates new content (a connector object) but does not execute code, trigger external systems, or permanently delete data.
From the tool's definition Tool modifies presentation by adding a connector between shapes, which creates or alters visual elements in the slide without deleting or executing external operations.
Documented attack patterns abuse exactly the kind of access connect_shapes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PowerPoint MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for connect_shapes:
{
"version": "1",
"default": "deny",
"tools": {
"connect_shapes": {
"limits": [
{
"counter": "connect_shapes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}connect_shapes 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.
Connect two shapes with a connector. It is categorised as a Write tool in the PowerPoint MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PowerPoint MCP Server MCP server in PolicyLayer and add a rule for connect_shapes: 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 MCP Server. Nothing to install.
connect_shapes 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 connect_shapes 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 connect_shapes. 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.
connect_shapes is provided by the PowerPoint MCP Server MCP server (jenstangen1/pptx-xlsx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PowerPoint MCP Server, 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.
37 PowerPoint MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.