rest_api_list_taxonomies

Zeigt alle registrierten Taxonomien mit REST API Support

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/c-sakel-wp-mcp-server/rest-api-list-taxonomies.md

WHAT IT DOES

What rest_api_list_taxonomies does on WordPress MCP Server

AI agents call rest_api_list_taxonomies to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why rest_api_list_taxonomies is rated Low

This tool queries and displays existing taxonomy information without modifying, executing operations, deleting data, or moving funds. It is a straightforward read operation on WordPress taxonomy registry data. The low severity reflects minimal blast radius—exposing taxonomy names and their REST API support status poses negligible security risk even if misused by an AI agent.

From the tool's definition Tool name 'rest_api_list_taxonomies' and description 'Zeigt alle registrierten Taxonomien mit REST API Support' (Shows all registered taxonomies with REST API support) indicate this retrieves and lists taxonomy metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rest_api_list_taxonomies safely

PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rest_api_list_taxonomies, this is the rule to start with:

rest_api_list_taxonomies Allowed

rest_api_list_taxonomies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rest_api_list_taxonomies": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every rest_api_list_taxonomies call is checked against it from then on.

FAQ

Questions about rest_api_list_taxonomies

What does the rest_api_list_taxonomies tool do? +

Zeigt alle registrierten Taxonomien mit REST API Support. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rest_api_list_taxonomies? +

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

What risk level is rest_api_list_taxonomies? +

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

Can I rate-limit rest_api_list_taxonomies? +

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

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

rest_api_list_taxonomies is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →