AI agents use create_connection to create or update resources in Querywise — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Querywise environment.
This tool creates a new connection object/configuration to a database. While it modifies system state by adding a connection, it does not execute queries, delete data, or commit financial transactions. The sibling tool 'delete_connection' confirms reversibility.
From the tool's definition Tool name 'create_connection' indicates creation of a new database connection configuration. Server description mentions connections to external databases (SQLite, PostgreSQL, BigQuery, Databricks).
Attacks that exploit this kind of access
create_connection. It is categorised as a Write tool in the Querywise MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Querywise MCP server in PolicyLayer and add a rule for create_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.
create_connection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →