AI agents call plan_evolutions to retrieve information from dexMCP 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 Pokémon evolution path data. It is a read-only lookup with no ability to modify, execute, or delete anything. Misuse potential is minimal as it only exposes game data.
From the tool's definition 'Enumerate evolution paths' — purely retrieves and lists data about Pokémon evolution chains with no side effects.
Attacks that exploit this kind of access
Enumerate evolution paths that include the Pokemon. It is categorised as a Read tool in the dexMCP MCP Server, which means it retrieves data without modifying state.
Register the dex MCP server in PolicyLayer and add a rule for plan_evolutions: 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 dexMCP. Nothing to install.
plan_evolutions 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 plan_evolutions 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 plan_evolutions. 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.
plan_evolutions is provided by the dex MCP server (rajeevatla/dexmcp). 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 →