AI agents call honeycomb_datasets_list to retrieve information from Honeycomb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves metadata about datasets. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an unauthorized user could discover what datasets exist in the environment but cannot alter them.
From the tool's definition Tool name contains 'list' and description states 'List all datasets'. The function retrieves and displays existing datasets without modifying or deleting data.
Attacks that exploit this kind of access
List all datasets in the environment. A Dataset represents a collection of related events that come from the same source, or are related to the same source. It is categorised as a Read tool in the Honeycomb MCP Server, which means it retrieves data without modifying state.
Register the Honeycomb MCP server in PolicyLayer and add a rule for honeycomb_datasets_list: 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 Honeycomb. Nothing to install.
honeycomb_datasets_list 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 honeycomb_datasets_list 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 honeycomb_datasets_list. 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.
honeycomb_datasets_list is provided by the Honeycomb MCP server (kajirita2002/honeycomb-mcp-server). 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 →