Get detailed information about a specific dataset version.
AI agents call get_dataset_version_details 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 metadata about a dataset version without modifying, executing, or deleting anything. It is a pure read operation with minimal blast radius if misused by an AI agent—worst case, an attacker gains information about dataset versions they may already have access to. It matches the 'Read' category pattern (get, fetch, query).
From the tool's definition Tool name is 'get_dataset_version_details' and description states 'Get detailed information about a specific dataset version.' This is a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get detailed information about a specific dataset version. 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 get_dataset_version_details: 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.
get_dataset_version_details 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 get_dataset_version_details 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 get_dataset_version_details. 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.
get_dataset_version_details 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 →