Low Risk

moxfield_deck_info

Get metadata for a Moxfield deck (name, format, author, dates). Returns deck metadata without the full card list. Use decklist for the complete card list.

Part of the MTG MCP Server server.

moxfield_deck_info is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MTG MCP SERVER →

Free to start. No card required.

AI agents call moxfield_deck_info 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 moxfield_deck_info 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "moxfield_deck_info": {}
  }
}

See the full MTG MCP Server policy for all 69 tools.

Get this rule live on your own MTG MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MTG MCP SERVER →

View all 69 tools →

These attack patterns abuse exactly the kind of access moxfield_deck_info gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so moxfield_deck_info only ever does what you allow.

SECURE MTG MCP SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the moxfield_deck_info tool do? +

Get metadata for a Moxfield deck (name, format, author, dates). Returns deck metadata without the full card list. Use decklist for the complete card list.. It is categorised as a Read tool in the MTG MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on moxfield_deck_info? +

Register the MTG MCP Server MCP server in PolicyLayer and add a rule for moxfield_deck_info: 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.

What risk level is moxfield_deck_info? +

moxfield_deck_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit moxfield_deck_info? +

Yes. Add a rate_limit block to the moxfield_deck_info 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.

How do I block moxfield_deck_info completely? +

Set action: deny in the PolicyLayer policy for moxfield_deck_info. 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.

What MCP server provides moxfield_deck_info? +

moxfield_deck_info 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.

Enforce policy on every MTG MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.