get_card

Look up a single Pokémon TCG (or other trading card game) card by its TCGdex id (e.g. "swsh3-136"). Returns full card details: category, rarity, hp, types, stage, set, illustrator, attacks, abilities, and a high-quality image URL.

Server Mcp Tcgdex pipeworx-io/mcp-tcgdex
Category Read
Risk class Low
Parameters 11 required

What get_card does on Mcp Tcgdex

AI agents call get_card 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.

ParameterTypeRequiredDescription
id string Yes TCGdex card id, e.g. "swsh3-136".

Parameters from the server's own tool schema.

Why get_card needs a policy

This tool queries a trading card database by ID and returns structured data about a card. It has no side effects, cannot modify data, execute code, or perform financial transactions. The worst-case misuse is retrieving public card information, which poses minimal risk. Confidence is high because the description explicitly characterizes this as a lookup/retrieval operation.

From the tool's definition Tool performs a lookup and returns card details (category, rarity, hp, types, stage, set, illustrator, attacks, abilities, image URL) with no modification capability. The verb is 'Look up' and the operation is purely retrieval-based.

Questions about get_card

What does the get_card tool do? +

Look up a single Pokémon TCG (or other trading card game) card by its TCGdex id (e.g. "swsh3-136"). Returns full card details: category, rarity, hp, types, stage, set, illustrator, attacks, abilities, and a high-quality image URL. It is categorised as a Read tool in the Mcp Tcgdex MCP Server, which means it retrieves data without modifying state.

What parameters does get_card accept? +

get_card accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_card? +

Register the Mcp Tcgdex 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 Tcgdex. Nothing to install.

What risk level is get_card? +

get_card is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_card? +

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.

How do I block get_card completely? +

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.

What MCP server provides get_card? +

get_card 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.