Modify existing table schema (add columns, rename tables, etc.)
AI agents use alter_table to create or update resources in MCP Database Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Database Server environment.
alter_table modifies table definitions through schema operations (add/rename columns). These are Write operations because they create or modify data structures reversibly. While schema changes can have broad impact (high severity), they remain in the Write category since ALTER TABLE operations are not destructive and can typically be reversed with subsequent ALTER operations.
From the tool's definition Tool description states 'Modify existing table schema (add columns, rename tables, etc.)' — this performs reversible modifications to database structures. The action is schema alteration, not deletion or destruction.
Attacks that exploit this kind of access
Modify existing table schema (add columns, rename tables, etc.). It is categorised as a Write tool in the MCP Database Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Database Server MCP server in PolicyLayer and add a rule for alter_table: 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 Database Server. Nothing to install.
alter_table 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 alter_table 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 alter_table. 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.
alter_table is provided by the MCP Database Server MCP server (suparn7/mcpserverwithsql). 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 →