AI agents invoke superset_query_stop to trigger actions in MCP Superset. 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.
This tool terminates an in-progress execution (a running async query), which is an operational action affecting external system state. It doesn't read or write data, but it does interrupt an ongoing execution process. Misuse could disrupt legitimate query operations.
From the tool's definition Stop a running asynchronous query
Documented attack patterns abuse exactly the kind of access superset_query_stop gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Superset, and nothing reaches the server without passing your rules. This is the rule we recommend for superset_query_stop:
{
"version": "1",
"default": "deny",
"tools": {
"superset_query_stop": {
"limits": [
{
"counter": "superset_query_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}superset_query_stop 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.
Stop a running asynchronous query. It is categorised as a Execute tool in the MCP Superset MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Superset MCP server in PolicyLayer and add a rule for superset_query_stop: 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 Superset. Nothing to install.
superset_query_stop 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 superset_query_stop 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 superset_query_stop. 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.
superset_query_stop is provided by the MCP Superset MCP server (mcp-superset). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Superset, 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.
137 MCP Superset tools catalogued and risk-classified — across an index of 43,000+ MCP servers.