Discovers all available taxonomies (built-in and custom) in the WordPress site
AI agents call discover_taxonomies to retrieve information from FluentCommunity Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs discovery/enumeration of WordPress taxonomy structures. It retrieves and lists information about taxonomies but does not create, modify, delete, or execute any operations. This is a pure read operation with minimal security impact—enumerating taxonomies is typically non-sensitive metadata that an authenticated WordPress user would normally be able to see anyway.
From the tool's definition Tool name 'discover_taxonomies' and description 'Discovers all available taxonomies (built-in and custom) in the WordPress site' indicate a read-only query operation that retrieves taxonomy metadata without modification or side effects.
Attacks that exploit this kind of access
Discovers all available taxonomies (built-in and custom) in the WordPress site. It is categorised as a Read tool in the FluentCommunity Manager MCP Server, which means it retrieves data without modifying state.
Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for discover_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 FluentCommunity Manager. Nothing to install.
discover_taxonomies 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 discover_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.
Set action: deny in the PolicyLayer policy for discover_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.
discover_taxonomies is provided by the FluentCommunity Manager MCP server (wplaunchify/fluent-community-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →