poke_search_pokemon
List Pokemon with pagination from PokeAPI.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/poke-search-pokemon.md
What poke_search_pokemon does on UnClick
AI agents call poke_search_pokemon to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Results per page (max 100, default 20) |
offset | number | — | Offset for pagination |
Parameters from the server's own tool schema.
Why poke_search_pokemon is rated Low
This tool queries and retrieves Pokemon data from a public API without side effects. It is purely informational and does not create, modify, delete, or execute operations. The pagination mechanism is a standard read pattern for managing result sets.
From the tool's definition Tool description states 'List Pokemon with pagination from PokeAPI' — a read-only retrieval operation with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
The rule that runs poke_search_pokemon safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For poke_search_pokemon, this is the rule to start with:
poke_search_pokemon is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every poke_search_pokemon call is checked against it from then on.
Questions about poke_search_pokemon
List Pokemon with pagination from PokeAPI. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
poke_search_pokemon accepts 2 parameters: limit, offset. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for poke_search_pokemon: 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 UnClick. Nothing to install.
poke_search_pokemon 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 poke_search_pokemon 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 poke_search_pokemon. 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.
poke_search_pokemon is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue