Low Risk

superset_database_tables

superset_database_tables

How to control superset_database_tables ↓

What superset_database_tables does on MCP Superset

AI agents call superset_database_tables to retrieve information from MCP Superset without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why superset_database_tables needs a policy

The tool appears to retrieve information about database tables in Superset, which is a read-only operation with no side effects. However, confidence is moderate (0.7) because the description is empty, preventing confirmation of exact functionality. If it returns sensitive schema information, blast radius remains low since no data is modified or deleted.

From the tool's definition Tool name 'superset_database_tables' indicates listing or fetching database table metadata. No verbs like 'create', 'delete', 'update', or 'execute' are present. The naming pattern aligns with retrieval operations (e.g., 'get', 'list').

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

How to control superset_database_tables

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "superset_database_tables": {}
  }
}

superset_database_tables is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about superset_database_tables

What does the superset_database_tables tool do? +

superset_database_tables. It is categorised as a Read tool in the MCP Superset MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on superset_database_tables? +

Register the MCP Superset MCP server in PolicyLayer and add a rule for superset_database_tables: 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_database_tables? +

superset_database_tables is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit superset_database_tables? +

Yes. Add a rate_limit block to the superset_database_tables 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_database_tables completely? +

Set action: deny in the PolicyLayer policy for superset_database_tables. 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_database_tables? +

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