根据预约人姓名删除预约记录
AI agents call delete_reservation_by_name to permanently remove resources in Reservation System MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes reservation records based on a name parameter. Deletion is irreversible and has no undo mechanism. The blast radius is high because a malicious or confused AI agent could delete multiple reservations matching a common name, causing operational disruption and data loss. While not financial, the destructive nature of permanent data removal makes this more severe than Write operations.
From the tool's definition Tool name contains 'delete' and description translates to 'Delete reservation records by reservee name' (根据预约人姓名删除预约记录). This irreversibly removes data from the WeChat Cloud-based reservation system.
Attacks that exploit this kind of access
根据预约人姓名删除预约记录. It is categorised as a Destructive tool in the Reservation System MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Reservation System MCP Server MCP server in PolicyLayer and add a rule for delete_reservation_by_name: 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 Reservation System MCP Server. Nothing to install.
delete_reservation_by_name 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 delete_reservation_by_name 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 delete_reservation_by_name. 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.
delete_reservation_by_name is provided by the Reservation System MCP Server MCP server (lingki1/mcp-reservation-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 →