Preview a dataset file by fetching a sample using the OpenHEXA GraphQL API.
AI agents call preview_dataset_file 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 displays sample data from a dataset file via the OpenHEXA GraphQL API. It has no side effects, does not modify data, execute code, delete content, or move money. The operation is purely informational - fetching a preview sample to enable users to understand dataset structure and content before further interaction. This is characteristic of Read category tools.
From the tool's definition Tool description states 'Preview a dataset file by fetching a sample' - the word 'preview' and 'fetching a sample' indicate data retrieval without modification.
Attacks that exploit this kind of access
Preview a dataset file by fetching a sample using the OpenHEXA GraphQL API. 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 preview_dataset_file: 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.
preview_dataset_file 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 preview_dataset_file 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 preview_dataset_file. 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.
preview_dataset_file 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 →