AI agents call introspect_connection 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.
Introspection of connection metadata is a read-only operation that retrieves information about existing database connections without modifying or executing arbitrary queries against live data. This aligns with the server's stated read-only default mode and falls squarely in the Read category. Severity is low because querying connection metadata poses minimal risk—it cannot delete, modify, or execute arbitrary code.
From the tool's definition Tool name 'introspect_connection' suggests querying metadata about an existing database connection (inspection of connection properties, status, or capabilities).
Attacks that exploit this kind of access
introspect_connection. It is categorised as a Read tool in the Querywise MCP Server, which means it retrieves data without modifying state.
Register the Querywise MCP server in PolicyLayer and add a rule for introspect_connection: 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.
introspect_connection 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 introspect_connection 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 introspect_connection. 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.
introspect_connection 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.
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 →