AI agents use ppt_add_section 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 and modifies presentation structure by adding a section, which is a reversible operation. It does not execute arbitrary code, delete data, or involve financial transactions. While it modifies the presentation, the change is easily undoable (sections can be removed), making it Write rather than Destructive.
From the tool's definition Tool name 'ppt_add_section' and description 'Add a section to the presentation' indicate creation of a new structural element within a PowerPoint presentation.
Documented attack patterns abuse exactly the kind of access ppt_add_section 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_add_section:
{
"version": "1",
"default": "deny",
"tools": {
"ppt_add_section": {
"limits": [
{
"counter": "ppt_add_section_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ppt_add_section 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.
Add a section to the presentation. 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_add_section: 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_add_section 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_add_section 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_add_section. 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_add_section 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.