Execute an INSERT, UPDATE, DELETE, or DDL query (requires FULL mode)
AI agents call sqlserver_execute to permanently remove resources in Multi-Database MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly supports DELETE and DDL operations (e.g., DROP TABLE, ALTER TABLE), which are irreversible and destructive. DDL commands like DROP or TRUNCATE can cause catastrophic data loss. Even UPDATE and DELETE without DDL qualify as high-severity. The combination of all these operation types, including DDL, elevates this to Destructive/critical.
From the tool's definition Execute an INSERT, UPDATE, DELETE, or DDL query
Attacks that exploit this kind of access
Execute an INSERT, UPDATE, DELETE, or DDL query (requires FULL mode). It is categorised as a Destructive tool in the Multi-Database MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for sqlserver_execute: 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 Multi-Database MCP Server. Nothing to install.
sqlserver_execute is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sqlserver_execute 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 sqlserver_execute. 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.
sqlserver_execute is provided by the Multi-Database MCP Server MCP server (nam088/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 →