AI agents use pptx_build_slide to create or update resources in Pptx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pptx environment.
The description is empty, so classification relies on the tool name and server context. 'Build slide' strongly implies creating or constructing a new slide within a presentation, which is a Write operation. Sibling tools are all write-oriented additions to presentations. Confidence is reduced due to the absent description.
From the tool's definition Tool name 'pptx_build_slide' on a server described as 'creating, reading, and editing PowerPoint (.pptx) presentations'; sibling tools are all write-oriented (add_chart, add_image, etc.)
Attacks that exploit this kind of access
pptx_build_slide. It is categorised as a Write tool in the Pptx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pptx MCP server in PolicyLayer and add a rule for pptx_build_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 Pptx. Nothing to install.
pptx_build_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 pptx_build_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 pptx_build_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.
pptx_build_slide is provided by the Pptx MCP server (knorq-ai/pptx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →