AI agents call mtg-export-format as a supporting operation in MTG-MCP workflows.
The description is empty and uninformative, making classification difficult. The name 'mtg-export-format' suggests it may format or export MTG data for output, which would be a Read/Write borderline operation. Given the MTG server context and sibling tools focused on reading card/deck data, this is most likely a Read or Write operation at low severity.
From the tool's definition Tool name is 'mtg-export-format' with an empty description. Based on the name alone, it likely formats or exports data.
Attacks that exploit this kind of access
mtg-export-format. It is categorised as a Other tool in the MTG-MCP MCP Server, which means it performs auxiliary operations.
Register the MTG- MCP server in PolicyLayer and add a rule for mtg-export-format: 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. Nothing to install.
mtg-export-format is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mtg-export-format 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 mtg-export-format. 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.
mtg-export-format is provided by the MTG- MCP server (wtfregia/mtg-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 →