pokeapi.type.matchup
Get the full damage relation chart for any of the 18 Pokemon types. Returns offensive relations (double/half/no damage TO other types) and defensive relations (double/half/no damage FROM other types). Also returns the total count of Pokemon and moves of that type. Valid types: normal, fighting, f...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/pokeapi.type.matchup.md
What pokeapi.type.matchup does on Apibase
AI agents call pokeapi.type.matchup 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 type name (e.g. "fire", "water", "grass", "electric", "dragon", "ghost") or numeric type ID (e.g. 10 for fire, 11 for water). Valid types: normal, fight |
Parameters from the server's own tool schema.
Why pokeapi.type.matchup is rated Low
Retrieves read-only Pokemon type matchup data; no side effects or state changes.
From the tool's definition Get the full damage relation chart for any Pokemon type. Returns offensive/defensive relations.
Attacks that exploit this kind of access
The rule that runs pokeapi.type.matchup 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.type.matchup, this is the rule to start with:
pokeapi.type.matchup 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.type.matchup call is checked against it from then on.
Questions about pokeapi.type.matchup
Get the full damage relation chart for any of the 18 Pokemon types. Returns offensive relations (double/half/no damage TO other types) and defensive relations (double/half/no damage FROM other types). Also returns the total count of Pokemon and moves of that type. Valid types: normal, fighting, flying, poison, ground, rock, bug, ghost, steel, fire, water, grass, electric, psychic, ice, dragon, dark, fairy. Useful for team building, battle strategy, and type-effectiveness calculators. 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.type.matchup 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.type.matchup: 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.type.matchup 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.type.matchup 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.type.matchup. 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.type.matchup 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