This record as markdown: /tools/c-sakel-wp-mcp-server/wp-list-tags.md
What wp_list_tags does on WordPress MCP Server
AI agents call wp_list_tags 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.
Why wp_list_tags is rated Low
This tool performs a retrieval operation only—it fetches and lists existing tags from WordPress. There are no side effects, no data modification, deletion, or execution of external operations. This is a straightforward Read operation with minimal security risk.
From the tool's definition Tool name 'wp_list_tags' and description 'Holt alle WordPress-Tags' (retrieves all WordPress tags) indicate a query operation that lists/retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs wp_list_tags 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 wp_list_tags, this is the rule to start with:
wp_list_tags is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every wp_list_tags call is checked against it from then on.
Questions about wp_list_tags
Holt alle WordPress-Tags. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wp_list_tags: 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.
wp_list_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wp_list_tags 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.
Set action: deny in the PolicyLayer policy for wp_list_tags. 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.
wp_list_tags 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.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue