List all tags in the AI Dictionary with term counts and sample terms.
AI agents call list_tags to retrieve information from Phenomenai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval of tag information from a glossary system. It returns counts and sample terms—informational data with no side effects, no data modification, and no external execution. The lowest severity applies because listing tags poses minimal risk; misuse would only expose existing, presumably public glossary metadata.
From the tool's definition Tool name 'list_tags' and description 'List all tags in the AI Dictionary with term counts and sample terms' indicate a query operation that retrieves metadata about existing tags without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List all tags in the AI Dictionary with term counts and sample terms. It is categorised as a Read tool in the Phenomenai MCP Server, which means it retrieves data without modifying state.
Register the Phenomenai MCP server in PolicyLayer and add a rule for 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 Phenomenai. Nothing to install.
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 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 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.
list_tags is provided by the Phenomenai MCP server (phenomenai-org/ai-dictionary-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 →