delete_record

删除表中的记录

Server MySQL MCP Server qipantanyi/mysql-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_record does on MySQL MCP Server

AI agents call delete_record to permanently remove resources in MySQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_record needs a policy

The tool deletes records from database tables, which is a destructive operation that cannot be undone. Even with stated security features like SQL injection protection, the fundamental capability is irreversible data removal.

From the tool's definition Tool name 'delete_record' and description indicating deletion of records from tables. This is an irreversible operation that removes data permanently.

Questions about delete_record

What does the delete_record tool do? +

删除表中的记录. It is categorised as a Destructive tool in the MySQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_record? +

Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for delete_record: 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.

What risk level is delete_record? +

delete_record is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_record? +

Yes. Add a rate_limit block to the delete_record 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.

How do I block delete_record completely? +

Set action: deny in the PolicyLayer policy for delete_record. 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.

What MCP server provides delete_record? +

delete_record is provided by the MySQL MCP Server MCP server (qipantanyi/mysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.