Delete an appointment by ID
AI agents call delete_appointment to permanently remove resources in Appointment Manager MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes appointment records from the database with no undo mechanism. Deletion is irreversible and cannot be recovered once executed. While not catastrophic at enterprise scale (unlike financial or infrastructure-level destructive operations), it permanently removes user data and meets the definition of a Destructive action.
From the tool's definition Tool name is 'delete_appointment' and description states 'Delete an appointment by ID'. The word 'Delete' is explicitly used, indicating irreversible removal of data from the PostgreSQL database.
Attacks that exploit this kind of access
Delete an appointment by ID. It is categorised as a Destructive tool in the Appointment Manager MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Appointment Manager MCP Server MCP server in PolicyLayer and add a rule for delete_appointment: 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 Appointment Manager MCP Server. Nothing to install.
delete_appointment 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_appointment 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_appointment. 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_appointment is provided by the Appointment Manager MCP Server MCP server (samuelr2112/mcp-project). 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 →