Low Risk

get_theme_json_property

Get the full spec for a specific theme.json property path. Accepts global paths (e.g.

How to control get_theme_json_property ↓

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

Low Risk

This tool retrieves specification information about theme.json properties from a documentation database. It performs a query/lookup operation with no side effects, no code execution, no data modification, and no destructive actions.

From the tool's definition Tool name 'get_theme_json_property' and description 'Get the full spec for a specific theme.json property path' indicate a retrieval operation with no modification or execution capabilities.

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

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

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

get_theme_json_property 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 Wp Devdocs — 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.

Go deeper

What does the get_theme_json_property tool do? +

Get the full spec for a specific theme.json property path. Accepts global paths (e.g. It is categorised as a Read tool in the Wp Devdocs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_theme_json_property? +

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

What risk level is get_theme_json_property? +

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

Can I rate-limit get_theme_json_property? +

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

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

get_theme_json_property is provided by the Wp Devdocs MCP server (pluginslab/wp-devdocs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wp Devdocs tool call.

Deterministic rules across all 9 Wp Devdocs tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

9 Wp Devdocs 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.