AI agents call find_encounters 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 retrieves Pokemon encounter location data from the underlying Pokemon database. It performs a query-like operation to return information about where a Pokemon can be found in the wild, similar to other read-only tools on the server (get_pokemon, get_moves, get_sprites, get_descriptions). There are no modifications, executions, deletions, or financial operations involved.
From the tool's definition Tool name 'find_encounters' and description 'Find wild encounter locations for a Pokemon' indicate a data retrieval operation.
Attacks that exploit this kind of access
Find wild encounter locations for a 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 find_encounters: 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.
find_encounters 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 find_encounters 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 find_encounters. 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.
find_encounters 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 →