Medium Risk

set_slide_background

set_slide_background

How to control set_slide_background ↓

AI agents use set_slide_background to create or update resources in Office Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Office Editor environment.

Medium Risk

The tool modifies presentation slide properties (background) reversibly. This is a Write operation: it changes document state but does not delete data, execute arbitrary code, or cause financial impact. Severity is low because changing a slide background has minimal blast radius—no data loss, no code execution, no external side effects.

From the tool's definition Tool name 'set_slide_background' on an office document editor server; sibling tools include 'add_slide', 'add_text_box', 'add_animation'—all Write operations. Description is empty.

Documented attack patterns abuse exactly the kind of access set_slide_background gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Office Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for set_slide_background:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_slide_background": {
      "limits": [
        {
          "counter": "set_slide_background_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Office Editor — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the set_slide_background tool do? +

set_slide_background. It is categorised as a Write tool in the Office Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_slide_background? +

Register the Office Editor MCP server in PolicyLayer and add a rule for set_slide_background: 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 Office Editor. Nothing to install.

What risk level is set_slide_background? +

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

Can I rate-limit set_slide_background? +

Yes. Add a rate_limit block to the set_slide_background 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 set_slide_background completely? +

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

set_slide_background is provided by the Office Editor MCP server (thewdy/office-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Office Editor tool call.

Deterministic rules across all 88 Office Editor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

88 Office Editor 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.