Parse a plain-text decklist into cards using Commander Spellbook.
AI agents invoke csb_parse_deck_text to trigger actions in Scryfall MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool parses input text and triggers external processing via the Commander Spellbook service to resolve card data. This goes beyond a simple read/query — it involves sending user-provided text to an external API for computation/transformation. It falls under Execute as it processes arbitrary input and invokes external operations, though the blast radius is moderate since it doesn't modify or delete data.
From the tool's definition 'Parse a plain-text decklist into cards using Commander Spellbook'
Attacks that exploit this kind of access
Parse a plain-text decklist into cards using Commander Spellbook. It is categorised as a Execute tool in the Scryfall MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Scryfall MCP Server MCP server in PolicyLayer and add a rule for csb_parse_deck_text: 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 Scryfall MCP Server. Nothing to install.
csb_parse_deck_text is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the csb_parse_deck_text 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 csb_parse_deck_text. 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.
csb_parse_deck_text is provided by the Scryfall MCP Server MCP server (latte-chan/scryfall-connector). 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 →