Query a dataset using Spark SQL dialect e.g. "SELECT COUNT(*) FROM dataset_rid"
AI agents invoke query_dataset to trigger actions in Foundry MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Although the example shows a SELECT, the tool executes arbitrary Spark SQL, which can include DDL/DML statements (INSERT, UPDATE, DELETE, DROP, etc.). Since it runs code whose effects depend on arguments and could be destructive, Execute is the most appropriate category. Severity is high because a malicious or erroneous query could corrupt or destroy dataset contents.
From the tool's definition Query a dataset using Spark SQL dialect e.g. "SELECT COUNT(*) FROM `dataset_rid`"
Documented attack patterns abuse exactly the kind of access query_dataset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Foundry MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_dataset:
{
"version": "1",
"default": "deny",
"tools": {
"query_dataset": {
"limits": [
{
"counter": "query_dataset_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}query_dataset stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Query a dataset using Spark SQL dialect e.g. "SELECT COUNT(*) FROM dataset_rid". It is categorised as a Execute tool in the Foundry MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Foundry MCP Server MCP server in PolicyLayer and add a rule for query_dataset: 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 Foundry MCP Server. Nothing to install.
query_dataset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the query_dataset 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 query_dataset. 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.
query_dataset is provided by the Foundry MCP Server MCP server (qwert666/mcp-server-foundry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Foundry MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Foundry MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.