Fetch record page and return seats with card details and match info (needs cookie for private cubes)
AI agents call get_record_decks 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 existing deck records and match information from CubeCobra. It performs a fetch operation that returns data (seats, card details, match info) without creating, modifying, deleting, or executing any operations. The tool is purely informational/read-only in nature, making it a Read category risk.
From the tool's definition Tool name 'get_record_decks' and description 'Fetch record page and return seats with card details and match info' indicate data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
Fetch record page and return seats with card details and match info (needs cookie for private cubes). 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_record_decks: 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_record_decks 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_record_decks 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_record_decks. 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_record_decks 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.
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 →