Filter rows in a Hugging Face dataset using SQL-like conditions
AI agents call filter 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.
Despite accepting SQL-like conditions, the tool is explicitly documented as filtering (querying) rows for analysis purposes on the Hugging Face Hub datasets. The operation is read-only: it retrieves and displays a filtered view of existing data without creating, modifying, or deleting any records.
From the tool's definition Tool description states it 'Filter rows in a Hugging Face dataset using SQL-like conditions' and is part of the Dataset Viewer MCP Server which 'enables interaction with the Hugging Face Dataset Viewer API, allowing users to browse, search, filter, and…
Documented attack patterns abuse exactly the kind of access filter 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 filter:
{
"version": "1",
"default": "deny",
"tools": {
"filter": {}
}
}filter 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.
Filter rows in a Hugging Face dataset using SQL-like conditions. 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 filter: 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.
filter 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 filter 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 filter. 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.
filter 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.