Medium Risk

edit_slides

Token-efficient partial edits on a previously-generated HTML deck. Use this INSTEAD of regenerating the whole deck for small changes — it saves 60-90% tokens vs a full rewrite. Operations: replace_slide (swap one slide block by 1-indexed slideIndex), patch_css (append CSS rules to <style>), swap_...

Accepts raw HTML/template content (payload); Single-target operation

Part of the Slideshot MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use edit_slides to create or modify resources in Slideshot. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call edit_slides repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Slideshot.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-06ketan-slideshot.yaml
tools:
  edit_slides:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Slideshot policy for all 6 tools.

Tool Name edit_slides
Category Write
Risk Level Medium

Agents calling write-class tools like edit_slides have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the edit_slides tool do? +

Token-efficient partial edits on a previously-generated HTML deck. Use this INSTEAD of regenerating the whole deck for small changes — it saves 60-90% tokens vs a full rewrite. Operations: replace_slide (swap one slide block by 1-indexed slideIndex), patch_css (append CSS rules to <style>), swap_token (replace a CSS variable's value, e.g. {"--coral": "#FF0000"}), patch_class (add/remove a class on a specific slide, e.g. {"add": "dark"}). Reads from cache or htmlPath; saves the updated HTML and returns the new htmlPath. After editing, show the htmlPath as a preview artifact and STOP — do NOT call render_slides until the user confirms.. It is categorised as a Write tool in the Slideshot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on edit_slides? +

Add a rule in your Intercept YAML policy under the tools section for edit_slides. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Slideshot MCP server.

What risk level is edit_slides? +

edit_slides is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit edit_slides? +

Yes. Add a rate_limit block to the edit_slides rule in your Intercept 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 edit_slides completely? +

Set action: deny in the Intercept policy for edit_slides. 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 edit_slides? +

edit_slides is provided by the Slideshot MCP server (slideshot-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.