AI agents invoke ppt_set_window_state 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.
This tool controls the PowerPoint application window state (e.g., minimized, maximized, restored) via COM automation. It triggers an external operation on the application UI rather than reading, writing document data, or performing destructive/financial actions. Severity is low since it only affects the window display state and has minimal blast radius.
From the tool's definition Set the PowerPoint application window state
Documented attack patterns abuse exactly the kind of access ppt_set_window_state 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_set_window_state:
{
"version": "1",
"default": "deny",
"tools": {
"ppt_set_window_state": {
"limits": [
{
"counter": "ppt_set_window_state_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ppt_set_window_state 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.
Set the PowerPoint application window state. 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_set_window_state: 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_set_window_state 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_set_window_state 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_set_window_state. 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_set_window_state 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.