AI agents use add_column to create or update resources in MCP-MongoDB-MySQL-Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-MongoDB-MySQL-Server environment.
This tool modifies database schema by adding columns to tables, which is a reversible write operation. While it alters table structure, it does not delete or overwrite existing data (making it Write rather than Destructive). The high severity reflects the potential for disruption to dependent applications and queries if columns are added with incorrect types or constraints.
From the tool's definition Tool name 'add_column' and description 'Add a new column to existing table' indicate a schema modification operation that creates new database structure.
Documented attack patterns abuse exactly the kind of access add_column gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-MongoDB-MySQL-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_column:
{
"version": "1",
"default": "deny",
"tools": {
"add_column": {
"limits": [
{
"counter": "add_column_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_column 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 new column to existing table. It is categorised as a Write tool in the MCP-MongoDB-MySQL-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-MongoDB-MySQL-Server MCP server in PolicyLayer and add a rule for add_column: 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 MCP-MongoDB-MySQL-Server. Nothing to install.
add_column 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 add_column 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 add_column. 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.
add_column is provided by the MCP-MongoDB-MySQL-Server MCP server (yaoxiaolinglong/mcp-mongodb-mysql-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-MongoDB-MySQL-Server, 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.
14 MCP-MongoDB-MySQL-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.