Search Yu-Gi-Oh! trading card game (TCG) cards by name (fuzzy), card type, attribute, monster race/type, archetype, or level. Returns matching cards with names, types, descriptions, ATK/DEF, attributes, archetypes, images, and TCGplayer card prices.
AI agents call search_cards to retrieve information from Mcp Ygoprodeck without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
num | number | — | Number of results to return (default 20, max 50). |
name | string | — | Fuzzy card name match, e.g. "Dark Magician", "Blue-Eyes". |
race | string | — | Monster type/race, e.g. 'Spellcaster', 'Dragon', 'Warrior'. For Spell/Trap, the property e.g. 'Continuous', 'Quick-Play'. |
type | string | — | Card type, e.g. 'Effect Monster', 'Normal Monster', 'Spell Card', 'Trap Card', 'XYZ Monster'. |
level | number | — | Monster level/rank, e.g. 7. |
offset | number | — | Pagination offset (default 0). |
archetype | string | — | Card archetype, e.g. "Blue-Eyes", "Dark Magician", "Sky Striker". |
attribute | string | — | Monster attribute, e.g. 'DARK', 'LIGHT', 'EARTH', 'WATER', 'FIRE', 'WIND', 'DIVINE'. |
Parameters from the server's own tool schema.
This tool retrieves and displays Yu-Gi-Oh! card data (names, types, prices, etc.) based on search criteria. It is a read-only query function with no ability to create, modify, delete, or execute code. Even in a misuse scenario, the worst an agent could do is exhaust API quotas or spam searches—no irreversible damage, financial transactions, or system-level operations are possible.
From the tool's definition Tool description explicitly states it "Search[es]" and "Returns matching cards" — purely a query operation with no side effects. No mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search Yu-Gi-Oh! trading card game (TCG) cards by name (fuzzy), card type, attribute, monster race/type, archetype, or level. Returns matching cards with names, types, descriptions, ATK/DEF, attributes, archetypes, images, and TCGplayer card prices. It is categorised as a Read tool in the Mcp Ygoprodeck MCP Server, which means it retrieves data without modifying state.
search_cards accepts 8 parameters: num, name, race, type, level, offset, archetype, attribute. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Ygoprodeck 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 Ygoprodeck. 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 Ygoprodeck MCP server (https://gateway.pipeworx.io/ygoprodeck/mcp). 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 →