Add a primary key to a table.
AI agents use mysql_add_primary_key to create or update resources in Mysql — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mysql environment.
Adding a primary key modifies table schema structure reversibly (can be removed with DROP CONSTRAINT or ALTER TABLE), placing it in the Write category rather than Destructive. However, this is a high-severity Write because it affects database structure and can have cascading effects on dependent queries and applications.
From the tool's definition Tool name 'mysql_add_primary_key' and description 'Add a primary key to a table' indicate a schema modification operation. Primary key constraints are structural database modifications that alter table definition.
Documented attack patterns abuse exactly the kind of access mysql_add_primary_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_add_primary_key:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_add_primary_key": {
"limits": [
{
"counter": "mysql_add_primary_key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mysql_add_primary_key stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a primary key to a table. It is categorised as a Write tool in the Mysql MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_add_primary_key: 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. Nothing to install.
mysql_add_primary_key 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_add_primary_key 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_add_primary_key. 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_add_primary_key is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mysql, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.