List all data cubes in the Imply project with their metadata.
AI agents call list_data_cubes to retrieve information from Imply Druid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about data cubes without executing queries, modifying data, or triggering side effects. Listing/enumeration operations are classic Read operations. The server's read-only designation confirms no Write, Execute, or Destructive capabilities exist. Severity is low because listing metadata poses minimal risk—it enables reconnaissance but causes no harm if misused by an AI agent.
From the tool's definition Tool name 'list_data_cubes' and description 'List all data cubes in the Imply project with their metadata' indicate retrieval of data without modification. Server is explicitly described as 'read-only'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all data cubes in the Imply project with their metadata. It is categorised as a Read tool in the Imply Druid MCP Server, which means it retrieves data without modifying state.
Register the Imply Druid MCP server in PolicyLayer and add a rule for list_data_cubes: 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 Imply Druid. Nothing to install.
list_data_cubes 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_data_cubes 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_data_cubes. 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_data_cubes is provided by the Imply Druid MCP server (yeongbin-hwang/imply-druid-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 →