set_brand · Keynote MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_brand does on Keynote MCP Server

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

WHY IT NEEDS A POLICY

Why set_brand needs a policy

The tool creates or updates brand configuration settings that affect how future design operations behave. This is a Write operation because it modifies state reversibly—the settings can be changed again or cleared. It does not execute arbitrary code, delete data, move money, or trigger external effects beyond the presentation system.

From the tool's definition Tool description states it 'Sets brand configuration' which modifies persistent configuration state for subsequent operations. This is a reversible creation/modification of data (brand settings) rather than deletion or code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_brand Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_brand": {
      "limits": [
        {
          "counter": "set_brand_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Keynote MCP Server, so you can run agents against it safely.

FAQ

Questions about set_brand

What does the set_brand tool do? +

Sets brand configuration for subsequent design_slide and design_deck operations. Values persist until changed or cleared. It is categorised as a Write tool in the Keynote MCP Server 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_brand? +

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

What risk level is set_brand? +

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

Can I rate-limit set_brand? +

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

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

set_brand is provided by the Keynote MCP Server MCP server (superdwayne/keynotemp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.