Fetches Scryfall Tagger tag names from the public docs page.
AI agents call list_tagger_tags 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 retrieves static tag name data from a public documentation page. It performs a read-only query with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only retrieve tag metadata that is already publicly available. No financial, destructive, write, or execute capabilities are present.
From the tool's definition Tool name 'list_tagger_tags' and description 'Fetches Scryfall Tagger tag names from the public docs page' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetches Scryfall Tagger tag names from the public docs page. 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 list_tagger_tags: 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.
list_tagger_tags 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 list_tagger_tags 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 list_tagger_tags. 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.
list_tagger_tags 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 →