Get detailed information about a Hugging Face dataset including description, features, splits, and statistics. Run validate first to check if the dataset exists and is accessible.
AI agents call get_info to retrieve information from Dataset Viewer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns metadata about datasets without creating, modifying, deleting, or executing any operations. It is a pure read operation with no side effects or ability to alter data. The low severity reflects that unauthorized access to public dataset metadata poses minimal risk.
From the tool's definition Tool description states it 'Get detailed information about a Hugging Face dataset including description, features, splits, and statistics' with no mention of modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access get_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dataset Viewer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_info": {}
}
}get_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information about a Hugging Face dataset including description, features, splits, and statistics. Run validate first to check if the dataset exists and is accessible. It is categorised as a Read tool in the Dataset Viewer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dataset Viewer MCP Server MCP server in PolicyLayer and add a rule for get_info: 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 Dataset Viewer MCP Server. Nothing to install.
get_info 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_info 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_info. 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_info is provided by the Dataset Viewer MCP Server MCP server (privetin/dataset-viewer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Dataset Viewer MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Dataset Viewer MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.