AI agents invoke ppt_slideshow_start to trigger actions in Ppt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Starting a slideshow is an action that executes/triggers an external operation in PowerPoint whose effects depend on presentation state and content. It is not a Read operation (does not merely query data), not Write (does not create/modify presentation data), not Destructive (does not delete/overwrite), and not Financial.
From the tool's definition Tool name 'ppt_slideshow_start' and description 'Start a slide show presentation' indicate execution of a presentation mode in PowerPoint, which triggers an external operation (launching slideshow).
Documented attack patterns abuse exactly the kind of access ppt_slideshow_start 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_slideshow_start:
{
"version": "1",
"default": "deny",
"tools": {
"ppt_slideshow_start": {
"limits": [
{
"counter": "ppt_slideshow_start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ppt_slideshow_start stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Start a slide show presentation. It is categorised as a Execute tool in the Ppt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ppt MCP server in PolicyLayer and add a rule for ppt_slideshow_start: 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_slideshow_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ppt_slideshow_start 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_slideshow_start. 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_slideshow_start 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.