Look up a single Yu-Gi-Oh! trading card game (TCG) card by its exact name. Returns full card details including type, description, ATK/DEF, level, attribute, archetype, banlist status, printed sets with rarities, and card prices (TCGplayer, Cardmarket, eBay, Amazon).
AI agents call get_card 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 |
|---|---|---|---|
name | string | Yes | Exact card name, e.g. "Dark Magician". |
Parameters from the server's own tool schema.
This tool purely retrieves and queries card information from a trading card database. It returns card details, specifications, and pricing data without creating, modifying, deleting, or executing any operations. The action is read-only with no side effects or ability to alter data state.
From the tool's definition The tool 'look up a single Yu-Gi-Oh! trading card game (TCG) card' and 'Returns full card details' and 'card prices' indicates data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Look up a single Yu-Gi-Oh! trading card game (TCG) card by its exact name. Returns full card details including type, description, ATK/DEF, level, attribute, archetype, banlist status, printed sets with rarities, and card prices (TCGplayer, Cardmarket, eBay, Amazon). It is categorised as a Read tool in the Mcp Ygoprodeck MCP Server, which means it retrieves data without modifying state.
get_card accepts 1 parameter: name. Required: name. 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 get_card: 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.
get_card 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 get_card 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 get_card. 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.
get_card 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 →