Insert new data into a table
AI agents use mysql_insert_data to create or update resources in MySQL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MySQL MCP Server environment.
INSERT operations create new records in a database table. While this modifies state, it is reversible—inserted data can be deleted or corrected—distinguishing it from destructive operations.
From the tool's definition Tool name 'mysql_insert_data' and description 'Insert new data into a table' indicate data creation via SQL INSERT operation. This is a reversible modification (data can be deleted or updated later).
Attacks that exploit this kind of access
Insert new data into a table. It is categorised as a Write tool in the MySQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for mysql_insert_data: 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 Server. Nothing to install.
mysql_insert_data 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 mysql_insert_data 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_insert_data. 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_insert_data is provided by the MySQL MCP Server MCP server (lakshya-saini/mysql-mcp-server). 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 →