Search Pokémon TCG (and other trading card games) cards by name in the TCGdex card database. Returns brief matches (id, localId, name, image thumbnail). Use get_card with an id for full card details.
AI agents call search_cards to retrieve information from Mcp Tcgdex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Card name or partial name to search for, e.g. "pikachu". Omit to list cards. |
limit | number | — | Max cards to return (default 30, max 100). |
Parameters from the server's own tool schema.
This tool queries a trading card game database to retrieve card information based on search criteria. It has no side effects—it reads and returns data without creating, modifying, deleting, or executing external operations. The search returns identifiers and metadata suitable for further queries (e.g., via get_card). This is a straightforward Read operation with minimal security risk.
From the tool's definition Tool performs a search query that 'Returns brief matches (id, localId, name, image thumbnail)' with no modification or deletion capabilities. The description explicitly indicates it retrieves data only.
Attacks that exploit this kind of access
Search Pokémon TCG (and other trading card games) cards by name in the TCGdex card database. Returns brief matches (id, localId, name, image thumbnail). Use get_card with an id for full card details. It is categorised as a Read tool in the Mcp Tcgdex MCP Server, which means it retrieves data without modifying state.
search_cards accepts 2 parameters: name, limit. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Tcgdex MCP server in PolicyLayer and add a rule for search_cards: 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 Tcgdex. Nothing to install.
search_cards 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 search_cards 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 search_cards. 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.
search_cards is provided by the Mcp Tcgdex MCP server (pipeworx-io/mcp-tcgdex). 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 →