Lists terms in any taxonomy (categories, tags, or custom taxonomies) with filtering and pagination
AI agents call list_terms 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 retrieves taxonomy terms from the WordPress system with filtering and pagination capabilities. It only reads data and produces no side effects, making it a Read operation. The severity is low because listing taxonomy terms exposes minimal sensitive information and cannot harm data or systems.
From the tool's definition Tool name 'list_terms' and description 'Lists terms in any taxonomy (categories, tags, or custom taxonomies) with filtering and pagination' indicate a query/retrieval operation with no data modification.
Attacks that exploit this kind of access
Lists terms in any taxonomy (categories, tags, or custom taxonomies) with filtering and pagination. 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 list_terms: 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.
list_terms 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 list_terms 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 list_terms. 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.
list_terms 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 →