Fetch cube JSON (cards + metadata)
AI agents call get_cube_json to retrieve information from CubeCobra 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 and queries Magic: The Gathering cube data from CubeCobra's API without modifying, deleting, or executing operations. The 'Fetch' verb and read-only nature of the operation clearly place it in the Read category. Low severity because exposure of cube metadata and card lists carries minimal risk to external systems or financial impact.
From the tool's definition Tool description explicitly states 'Fetch cube JSON (cards + metadata)' - a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch cube JSON (cards + metadata). It is categorised as a Read tool in the CubeCobra MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CubeCobra MCP Server MCP server in PolicyLayer and add a rule for get_cube_json: 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 CubeCobra MCP Server. Nothing to install.
get_cube_json 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 get_cube_json 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 get_cube_json. 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.
get_cube_json is provided by the CubeCobra MCP Server MCP server (plrdev/cubecobra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_cube_json is one line of CubeCobra MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →