Get connection information (URI without password, parameters).
AI agents call superset_database_connection_info 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.
This tool retrieves connection information (URI and parameters) about a database connection. While it is a Read operation with no side effects, the severity is elevated to medium because connection URIs and parameters could reveal sensitive infrastructure details (hostnames, ports, database names, usernames) that could facilitate reconnaissance or lateral movement attacks, even though passwords are explicitly…
From the tool's definition Tool name includes 'get' operation and description states 'Get connection information', retrieving data without modification.
Documented attack patterns abuse exactly the kind of access superset_database_connection_info 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_connection_info:
{
"version": "1",
"default": "deny",
"tools": {
"superset_database_connection_info": {}
}
} superset_database_connection_info 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.
Get connection information (URI without password, parameters). 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_connection_info: 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_connection_info 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_connection_info 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_connection_info. 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_connection_info 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.