list_connections

list_connections

Server Querywise kosminus/querywise-mcp
Category Read
Risk class Low
Parameters 00 required

What list_connections does on Querywise

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

Why list_connections needs a policy

This tool retrieves and displays existing database connection configurations, which is a non-destructive read operation. There is no ability to modify, execute queries, or delete connections (separate tools handle those operations). The blast radius is minimal—it exposes connection metadata but does not execute commands or alter state.

From the tool's definition Tool name 'list_connections' indicates a query/enumeration operation. The server description states it is 'Read-only by default' and provides a mechanism to manage database connections. The 'list' verb denotes data retrieval with no modification.

Questions about list_connections

What does the list_connections tool do? +

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

How do I enforce a policy on list_connections? +

Register the Querywise MCP server in PolicyLayer and add a rule for list_connections: 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 Querywise. Nothing to install.

What risk level is list_connections? +

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

Can I rate-limit list_connections? +

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

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

list_connections is provided by the Querywise MCP server (kosminus/querywise-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.