Get detailed information about a specific card by exact name
AI agents call get_card_details to retrieve information from Scryfall MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a read-only database to return card information. The action is non-destructive, non-financial, and produces no side effects beyond returning requested data. Even if misused by an AI agent, it cannot harm the system, data integrity, or user interests. Severity is low because the worst outcome is retrieving unwanted information, which has minimal blast radius.
From the tool's definition Tool 'get_card_details' retrieves detailed information about a specific card by exact name from Scryfall's database. This is purely a query/retrieval operation with no side effects—it 'Get[s] detailed information' without modifying, creating, or deleting data.
Attacks that exploit this kind of access
Get detailed information about a specific card by exact name. It is categorised as a Read tool in the Scryfall MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Scryfall MCP Server MCP server in PolicyLayer and add a rule for get_card_details: 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.
get_card_details 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_details 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_details. 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_details is provided by the Scryfall MCP Server MCP server (joemocode/scryfall-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 →