Medium Risk

superset_saved_query_update

Update a saved query. Pass only the fields to change.

How to control superset_saved_query_update ↓

What superset_saved_query_update does on MCP Superset

AI agents use superset_saved_query_update to create or update resources in MCP Superset — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Superset environment.

Medium Risk

Why superset_saved_query_update needs a policy

This tool modifies an existing saved query in Superset. It is a reversible write operation (the query can be updated again or reverted). No code execution, deletion, or financial action is involved.

From the tool's definition "Update a saved query. Pass only the fields to change."

Documented attack patterns abuse exactly the kind of access superset_saved_query_update gives an agent:

How to control superset_saved_query_update

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_saved_query_update:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "superset_saved_query_update": {
      "limits": [
        {
          "counter": "superset_saved_query_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

superset_saved_query_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Superset — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about superset_saved_query_update

What does the superset_saved_query_update tool do? +

Update a saved query. Pass only the fields to change. It is categorised as a Write tool in the MCP Superset MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on superset_saved_query_update? +

Register the MCP Superset MCP server in PolicyLayer and add a rule for superset_saved_query_update: 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.

What risk level is superset_saved_query_update? +

superset_saved_query_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit superset_saved_query_update? +

Yes. Add a rate_limit block to the superset_saved_query_update 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.

How do I block superset_saved_query_update completely? +

Set action: deny in the PolicyLayer policy for superset_saved_query_update. 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.

What MCP server provides superset_saved_query_update? +

superset_saved_query_update 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.

Enforce policy on every MCP Superset tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.