Get AI Dictionary metadata: term count, tag count, last updated, and API info.
AI agents call dictionary_stats 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 queries and returns informational statistics about the dictionary without altering any data or triggering side effects. It is a simple retrieval operation that fits the 'Read' category. The low severity reflects that misuse would only expose statistics that are likely already public or non-sensitive metadata.
From the tool's definition Tool description states it retrieves metadata: 'term count, tag count, last updated, and API info.' The verb 'Get' indicates read-only data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get AI Dictionary metadata: term count, tag count, last updated, and API info. 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 dictionary_stats: 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.
dictionary_stats 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 dictionary_stats 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 dictionary_stats. 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.
dictionary_stats 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 →