Execute a SQL query against a MySQL database. The query will be validated against the configured permissions for the database before execution. Available permissions: - SELECT: Read data from tables - INSERT: Insert new data into tables - UPDATE: Update existing data in tables - DELETE: Delete da...
AI agents invoke mysql_query to trigger actions in Mysql Mcp Webui. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary SQL queries covering the full spectrum of database operations. It can perform destructive operations (DROP, TRUNCATE, DELETE), structural modifications (CREATE, ALTER), and data manipulation (INSERT, UPDATE).
From the tool's definition 'Execute a SQL query against a MySQL database' with permissions including SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, TRUNCATE
Attacks that exploit this kind of access
Execute a SQL query against a MySQL database. The query will be validated against the configured permissions for the database before execution. Available permissions: - SELECT: Read data from tables - INSERT: Insert new data into tables - UPDATE: Update existing data in tables - DELETE: Delete data from tables - CREATE: Create new database objects (tables, indexes, etc.) - ALTER: Modify existing database structure - DROP: Drop database objects - TRUNCATE: Truncate tables The query runs within a transaction and will be rolled back if it fails. The database will be automatically activated if not already active. Use the alias (not the actual database name) to specify the database. It is categorised as a Execute tool in the Mysql Mcp Webui MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mysql Mcp Webui MCP server in PolicyLayer and add a rule for mysql_query: 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 Mysql Mcp Webui. Nothing to install.
mysql_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mysql_query 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 mysql_query. 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.
mysql_query is provided by the Mysql Mcp Webui MCP server (yashagldit/mysql-mcp-webui). 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 →