Connect an external database as a data source in MindsDB.
AI agents use connect_database to create or update resources in MindsDB MySQL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MindsDB MySQL MCP Server environment.
This tool creates a new database connection configuration in MindsDB, which is reversible (the connection can be removed/disconnected). While it modifies system state and could enable downstream attacks via connected data sources, it does not directly execute queries, delete data, or move funds.
From the tool's definition Tool performs 'Connect an external database as a data source' which creates or registers a new data source connection in MindsDB, modifying the system's configuration state.
Attacks that exploit this kind of access
Connect an external database as a data source in MindsDB. It is categorised as a Write tool in the MindsDB MySQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MindsDB MySQL MCP Server MCP server in PolicyLayer and add a rule for connect_database: 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 MindsDB MySQL MCP Server. Nothing to install.
connect_database 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 connect_database 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 connect_database. 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.
connect_database is provided by the MindsDB MySQL MCP Server MCP server (nikhgupta/mindsdb-mysql-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 →