List recent tournaments for a format with dates, player counts, and IDs. Use the tournament ID from the results with tournament_results to see full standings and decklists.
Part of the MTG MCP Server server.
Free to start. No card required.
AI agents call spicerack_recent_tournaments to retrieve information from MTG MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though spicerack_recent_tournaments only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"spicerack_recent_tournaments": {}
}
}See the full MTG MCP Server policy for all 69 tools.
These attack patterns abuse exactly the kind of access spicerack_recent_tournaments gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List recent tournaments for a format with dates, player counts, and IDs. Use the tournament ID from the results with tournament_results to see full standings and decklists.. It is categorised as a Read tool in the MTG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MTG MCP Server MCP server in PolicyLayer and add a rule for spicerack_recent_tournaments: 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 MTG MCP Server. Nothing to install.
spicerack_recent_tournaments 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 spicerack_recent_tournaments 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 spicerack_recent_tournaments. 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.
spicerack_recent_tournaments is provided by the MTG MCP Server MCP server (pypi:mtg-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 69 MTG MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.