Low Risk

list_themes

List installed WordPress themes with status. Requires: API key with read scope. WordPress sites only. Args: slug: Site identifier Returns: {"themes": [{"name": "twentytwentyfour", "status": "active", "version": "1.0", "update_available": false}, ...]}

Part of the BorealHost server.

list_themes is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE BOREALHOST →

Free to start. No card required.

AI agents call list_themes to retrieve information from BorealHost without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_themes only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full BorealHost policy for all 95 tools.

Get this rule live on your own BorealHost server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY BOREALHOST →

View all 95 tools →

These attack patterns abuse exactly the kind of access list_themes gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so list_themes only ever does what you allow.

SECURE BOREALHOST →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the list_themes tool do? +

List installed WordPress themes with status. Requires: API key with read scope. WordPress sites only. Args: slug: Site identifier Returns: {"themes": [{"name": "twentytwentyfour", "status": "active", "version": "1.0", "update_available": false}, ...]}. It is categorised as a Read tool in the BorealHost MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_themes? +

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

What risk level is list_themes? +

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

Can I rate-limit list_themes? +

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

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

list_themes is provided by the BorealHost MCP server (pypi:borealhost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BorealHost tool call.

Deterministic rules across all 95 BorealHost tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.