High Risk →

ppt_slideshow_previous

Go back to the previous slide in the running slide show.

How to control ppt_slideshow_previous ↓

AI agents invoke ppt_slideshow_previous 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.

High Risk

This tool triggers an external operation (navigating a live PowerPoint slideshow via COM automation). It doesn't read data, write/create content, or destroy anything — it executes a navigation action in a running presentation session. Severity is low since the blast radius is minimal: it only moves the slideshow back one slide.

From the tool's definition Go back to the previous slide in the running slide show

Documented attack patterns abuse exactly the kind of access ppt_slideshow_previous 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_previous:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ppt_slideshow_previous": {
      "limits": [
        {
          "counter": "ppt_slideshow_previous_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

ppt_slideshow_previous 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.

  1. Create a free account and register Ppt — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the ppt_slideshow_previous tool do? +

Go back to the previous slide in the running slide show. 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.

How do I enforce a policy on ppt_slideshow_previous? +

Register the Ppt MCP server in PolicyLayer and add a rule for ppt_slideshow_previous: 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.

What risk level is ppt_slideshow_previous? +

ppt_slideshow_previous is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ppt_slideshow_previous? +

Yes. Add a rate_limit block to the ppt_slideshow_previous 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.

How do I block ppt_slideshow_previous completely? +

Set action: deny in the PolicyLayer policy for ppt_slideshow_previous. 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.

What MCP server provides ppt_slideshow_previous? +

ppt_slideshow_previous 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.

Enforce policy on every Ppt tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.