AI agents call superset_database_table_metadata 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.
The tool name strongly suggests fetching metadata about database tables, which is a read-only operation with no side effects. The empty description reduces confidence slightly, but the naming pattern and context of sibling tools (which include explicit CRUD operations) support classifying this as a Read operation with low severity since metadata queries typically expose non-sensitive structural information.
From the tool's definition Tool name 'superset_database_table_metadata' indicates retrieval of table metadata; sibling tools use explicit verbs (create, delete, get, list, update) and this tool lacks a mutation verb, suggesting a query/fetch operation.
Documented attack patterns abuse exactly the kind of access superset_database_table_metadata 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_database_table_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"superset_database_table_metadata": {}
}
}superset_database_table_metadata 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.
superset_database_table_metadata. It is categorised as a Read tool in the MCP Superset MCP Server, which means it retrieves data without modifying state.
Register the MCP Superset MCP server in PolicyLayer and add a rule for superset_database_table_metadata: 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_database_table_metadata 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 superset_database_table_metadata 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_database_table_metadata. 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_database_table_metadata 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.