Find cards using Tagger function (oracle) tags, e.g. removal, ramp.
AI agents call search_by_function_tag 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 performs a search/query operation that retrieves card data based on specified function tags (removal, ramp, etc.). It has no side effects—it neither modifies data, executes arbitrary code, deletes anything, nor commits financial transactions. The worst-case misuse scenario is retrieving unwanted card information, which poses negligible risk.
From the tool's definition Tool enables searching and retrieving Magic: The Gathering card data through function/oracle tags; described as finding cards, with no capability to modify, delete, or execute operations.
Attacks that exploit this kind of access
Find cards using Tagger function (oracle) tags, e.g. removal, ramp. 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 search_by_function_tag: 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.
search_by_function_tag 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 search_by_function_tag 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 search_by_function_tag. 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.
search_by_function_tag 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 →