AI agents invoke ppt_select_shapes to trigger actions in Ppt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Selecting shapes triggers an external operation in PowerPoint via COM automation (changes the application's selection state). It does not read data back to the agent, does not persistently modify document content, and is not destructive—but it does actuate a live application state change, fitting Execute. Blast radius is low since selection alone does not alter the document.
From the tool's definition Select multiple shapes on a slide by name
Documented attack patterns abuse exactly the kind of access ppt_select_shapes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ppt, and nothing reaches the server without passing your rules. This is the rule we recommend for ppt_select_shapes:
{
"version": "1",
"default": "deny",
"tools": {
"ppt_select_shapes": {
"limits": [
{
"counter": "ppt_select_shapes_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ppt_select_shapes stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Select multiple shapes on a slide by name. It is categorised as a Execute tool in the Ppt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ppt MCP server in PolicyLayer and add a rule for ppt_select_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 Ppt. Nothing to install.
ppt_select_shapes is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ppt_select_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 ppt_select_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.
ppt_select_shapes is provided by the Ppt MCP server (ykuwai/ppt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 156 Ppt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
156 Ppt tools catalogued and risk-classified — across an index of 42,500+ MCP servers.