AI agents use ppt_distribute_shapes to create or update resources in Ppt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ppt environment.
This tool creates or modifies the spatial arrangement of existing shapes on a slide. The changes are reversible (shapes can be repositioned again), so it falls under Write rather than Destructive. The blast radius is medium because misuse could degrade presentation aesthetics or confuse slide layouts, but the effect is not irreversible and does not involve deletion, financial impact, or arbitrary code execution.
From the tool's definition Tool description states 'Distribute shapes evenly on a slide' — this modifies the visual layout and positioning of shapes within a presentation, which is a reversible data modification operation.
Documented attack patterns abuse exactly the kind of access ppt_distribute_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_distribute_shapes:
{
"version": "1",
"default": "deny",
"tools": {
"ppt_distribute_shapes": {
"limits": [
{
"counter": "ppt_distribute_shapes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ppt_distribute_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.
Distribute shapes evenly on a slide. It is categorised as a Write tool in the Ppt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ppt MCP server in PolicyLayer and add a rule for ppt_distribute_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_distribute_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 ppt_distribute_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_distribute_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_distribute_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.