Get details about a Pokémon move.
AI agents call pokedex_move to retrieve information from Mcp Everything without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only information about a Pokémon move from what is likely the PokéAPI or similar data source. It has no side effects, modifies nothing, and simply fetches descriptive data. Severity is low as misuse has negligible real-world impact.
From the tool's definition Get details about a Pokémon move
Attacks that exploit this kind of access
Get details about a Pokémon move. It is categorised as a Read tool in the Mcp Everything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Everything MCP server in PolicyLayer and add a rule for pokedex_move: 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 Mcp Everything. Nothing to install.
pokedex_move 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 pokedex_move 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 pokedex_move. 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.
pokedex_move is provided by the Mcp Everything MCP server (wellix260/mcp-everything). 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 →