Low Risk

get_theme_colors

Return the named color slots from word/theme/theme1.xml.

How to control get_theme_colors ↓

What get_theme_colors does on Docx

AI agents call get_theme_colors to retrieve information from Docx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_theme_colors needs a policy

This tool retrieves theme color information from a Word document's XML structure. 'Return' and 'get' are read-only operations. No document state is altered, no code is executed, and no data is deleted or created. The low severity reflects that color theme data is non-sensitive structural information with minimal blast radius if exposed to an AI agent.

From the tool's definition Tool name 'get_theme_colors' and description 'Return the named color slots from word/theme/theme1.xml' indicate a retrieval operation that queries document theme data without modification or side effects.

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

How to control get_theme_colors

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_theme_colors": {}
  }
}

get_theme_colors is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_theme_colors

What does the get_theme_colors tool do? +

Return the named color slots from word/theme/theme1.xml. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_theme_colors? +

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

What risk level is get_theme_colors? +

get_theme_colors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_theme_colors? +

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

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

get_theme_colors is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docx tool call.

Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

219 Docx tools catalogued and risk-classified — across an index of 43,000+ 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.