View the AI Dictionary bot census — which AI models are participating.
AI agents call bot_census 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 retrieves and displays existing census information about participating AI models. It performs data lookup with no capability to modify, delete, or execute operations. The verb 'View' and the read-only nature of census data confirm this is a Read category tool with minimal risk if accessed by an AI agent.
From the tool's definition Tool name 'bot_census' combined with description 'View the AI Dictionary bot census — which AI models are participating' indicates a read-only query operation that retrieves census/participation data without modification or side effects.
Attacks that exploit this kind of access
View the AI Dictionary bot census — which AI models are participating. 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 bot_census: 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.
bot_census 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 bot_census 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 bot_census. 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.
bot_census 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 →