pokeapi.pokemon.detail
Get detailed data for any of 1025+ Pokemon by name or Pokedex ID. Returns: types (e.g. fire/flying), base stats (HP, Attack, Defense, Sp.Atk, Sp.Def, Speed), abilities (including hidden ability), first 20 moves, height (dm), weight (hg), base experience, and sprite image URLs. Examples: "pikachu"...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/pokeapi.pokemon.detail.md
What pokeapi.pokemon.detail does on Apibase
AI agents call pokeapi.pokemon.detail to retrieve information from Apibase 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 |
|---|---|---|---|
name_or_id | string | number | Yes | Pokemon name (e.g. "pikachu", "charizard") or numeric Pokedex ID (e.g. 25, 6). Names are case-insensitive. Hyphenated forms accepted (e.g. "mr-mime", "tapu-koko |
Parameters from the server's own tool schema.
Why pokeapi.pokemon.detail is rated Low
Tool retrieves static Pokemon data from a public API without side effects or data modification.
From the tool's definition Get detailed data for any of 1025+ Pokemon by name or Pokedex ID. Returns: types, base stats, abilities, moves, height, weight, base experience, and sprite image URLs.
Attacks that exploit this kind of access
The rule that runs pokeapi.pokemon.detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pokeapi.pokemon.detail, this is the rule to start with:
pokeapi.pokemon.detail 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 Apibase, apply this rule, and every pokeapi.pokemon.detail call is checked against it from then on.
Questions about pokeapi.pokemon.detail
Get detailed data for any of 1025+ Pokemon by name or Pokedex ID. Returns: types (e.g. fire/flying), base stats (HP, Attack, Defense, Sp.Atk, Sp.Def, Speed), abilities (including hidden ability), first 20 moves, height (dm), weight (hg), base experience, and sprite image URLs. Examples: "pikachu" (id 25), "charizard" (id 6), "mewtwo" (id 150), "eevee" (id 133). Hyphenated names accepted: "mr-mime", "tapu-koko", "jangmo-o". No auth required; fair-use free API. Source: PokéAPI (pokeapi.co). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
pokeapi.pokemon.detail accepts 1 parameter: name_or_id. Required: name_or_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for pokeapi.pokemon.detail: 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 Apibase. Nothing to install.
pokeapi.pokemon.detail 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 pokeapi.pokemon.detail 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 pokeapi.pokemon.detail. 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.
pokeapi.pokemon.detail is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue