Edit an existing PowerPoint (.pptx). Actions:
AI agents use edit-pptx to create or update resources in MCP Document Processor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Document Processor environment.
The tool modifies existing PowerPoint documents, which is a reversible Write action. It does not delete or irreversibly destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve information (Read). The medium severity reflects that accidental edits could corrupt presentation content, but changes remain recoverable through document history or backups.
From the tool's definition Tool name 'edit-pptx' combined with description 'Edit an existing PowerPoint (.pptx)' directly indicates modification of existing files. The word 'Edit' explicitly signals a write operation that alters document content reversibly.
Attacks that exploit this kind of access
Edit an existing PowerPoint (.pptx). Actions:. It is categorised as a Write tool in the MCP Document Processor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Document Processor MCP server in PolicyLayer and add a rule for edit-pptx: 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 MCP Document Processor. Nothing to install.
edit-pptx 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 edit-pptx 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 edit-pptx. 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.
edit-pptx is provided by the MCP Document Processor MCP server (leanzero-srl/leanzero-mcp-doc-processor). 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 →