list_datasets
AI agents call list_datasets to retrieve information from Mcp Openhexa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool lists datasets, which is a retrieval operation with no side effects. It queries data from the OpenHEXA platform without modifying, executing code, or deleting anything. The empty description is mitigated by the clear semantic meaning of 'list' and the context of sibling Read-category tools. Severity is low because listing datasets presents minimal risk of harm if misused by an AI agent.
From the tool's definition Tool name 'list_datasets' combined with server description stating 'list datasets' as a capability. The tool is grouped with other Read operations (get_dataset_details, list_dataset_files, list_dataset_versions, list_connections, get_workspace_details) that…
Attacks that exploit this kind of access
list_datasets. It is categorised as a Read tool in the Mcp Openhexa MCP Server, which means it retrieves data without modifying state.
Register the Mcp Openhexa MCP server in PolicyLayer and add a rule for list_datasets: 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 Mcp Openhexa. Nothing to install.
list_datasets 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_datasets 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_datasets. 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_datasets is provided by the Mcp Openhexa MCP server (mcrimi/mcp-openhexa). 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 →