mtg_search_cards
Search Magic: The Gathering cards by name, color, type, set, or rarity.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mtg-search-cards.md
What mtg_search_cards does on UnClick
AI agents call mtg_search_cards to retrieve information from UnClick 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 |
|---|---|---|---|
set | string | — | Set code (e.g. LEA, M21). |
name | string | — | Card name to search. |
type | string | — | Card type (e.g. Instant, Creature, Sorcery). |
limit | number | — | Max results (default 10). |
colors | string | — | Color filter (W, U, B, R, G or combinations). |
rarity | string | — | Rarity: common, uncommon, rare, mythic. |
Parameters from the server's own tool schema.
Why mtg_search_cards is rated Low
This tool retrieves card data from a Magic: The Gathering database based on filter criteria. It is purely informational with no capacity to modify, delete, execute, or create financial obligations. Search and query operations fall squarely into the Read category.
From the tool's definition Tool description states "Search Magic: The Gathering cards by name, color, type, set, or rarity" - a query/search operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs mtg_search_cards safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mtg_search_cards, this is the rule to start with:
mtg_search_cards 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 UnClick, apply this rule, and every mtg_search_cards call is checked against it from then on.
Questions about mtg_search_cards
Search Magic: The Gathering cards by name, color, type, set, or rarity. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mtg_search_cards accepts 6 parameters: set, name, type, limit, colors, rarity. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for mtg_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 UnClick. Nothing to install.
mtg_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 mtg_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 mtg_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.
mtg_search_cards is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue