ppt_create
Creates a PowerPoint (.pptx) file with title and bullet slides.
This record as markdown: /tools/com-local-mcp-local-mcp/ppt-create.md
What ppt_create does on Local
AI agents use ppt_create to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Output path for the .pptx file |
slides | array | Yes | Array of {title, bullets:[]} slide objects |
confirm | boolean | — | Must be true to create |
Parameters from the server's own tool schema.
Why ppt_create is rated Medium
Creating a PowerPoint file is a write operation that generates new data on disk. It is reversible (the file can be deleted) and has no financial impact, so it falls under Write rather than Destructive.
From the tool's definition Tool name 'ppt_create' and description states it 'Creates a PowerPoint (.pptx) file' — this is file creation/generation that modifies the local filesystem.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs ppt_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ppt_create, this is the rule to start with:
ppt_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every ppt_create call is checked against it from then on.
Questions about ppt_create
Creates a PowerPoint (.pptx) file with title and bullet slides. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
ppt_create accepts 3 parameters: path, slides, confirm. Required: path, slides. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for ppt_create: 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 Local. Nothing to install.
ppt_create 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_create 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_create. 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_create is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue