List all files for all versions of a dataset.
AI agents call list_dataset_files 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 retrieves and queries file metadata from datasets without modifying, deleting, or executing any operations. It is a passive information retrieval function, consistent with the 'Read' category. No side effects occur from calling this tool. Severity is low because listing files presents minimal risk even if misused by an AI agent—the worst outcome is disclosure of file names and metadata.
From the tool's definition Tool name 'list_dataset_files' and description 'List all files for all versions of a dataset' indicate a retrieval operation with no modification or execution capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all files for all versions of a dataset. 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_dataset_files: 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_dataset_files 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_dataset_files 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_dataset_files. 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_dataset_files 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 →