List cube records (requires CubeCobra session cookie + CSRF for private/owner data)
AI agents call list_cube_records 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 cube record data from the CubeCobra API. It performs no side effects—no data is created, modified, deleted, or executed. The authentication requirement is a security mechanism to control read access, not an indicator of a different risk category. The tool fits the 'Read' category as it queries existing data without reversible or irreversible changes.
From the tool's definition Tool name 'list_cube_records' and description 'List cube records' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
List cube records (requires CubeCobra session cookie + CSRF for private/owner data). 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 list_cube_records: 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.
list_cube_records 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 list_cube_records 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 list_cube_records. 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.
list_cube_records 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 →