Clear/delete a schedule item by its row number
AI agents call delete_schedule to permanently remove resources in Wedding Planner MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes wedding schedule entries without reversibility. While the blast radius is confined to wedding planning data rather than critical systems, the irreversible nature of deletion and potential to disrupt wedding timelines by removing important schedule items (venue setup times, ceremony start, photo sessions, etc.) justifies 'Destructive' categorization and 'high' severity.
From the tool's definition Tool name explicitly includes 'delete' and description states 'Clear/delete a schedule item by its row number'. The action irreversibly removes scheduled wedding planning data.
Attacks that exploit this kind of access
Clear/delete a schedule item by its row number. It is categorised as a Destructive tool in the Wedding Planner MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wedding Planner MCP Server MCP server in PolicyLayer and add a rule for delete_schedule: 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 Wedding Planner MCP Server. Nothing to install.
delete_schedule 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_schedule 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_schedule. 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_schedule is provided by the Wedding Planner MCP Server MCP server (kiboud/weddingplanner_mcp). 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 →