delete_coordination

Clear/delete a coordination item by its row number

Server Wedding Planner MCP Server kiboud/weddingplanner_mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_coordination does on Wedding Planner MCP Server

AI agents call delete_coordination 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.

Why delete_coordination needs a policy

This tool permanently removes coordination items from the Google Sheets backend without apparent undo capability. While the blast radius is limited to a single wedding's coordination data (not organization-wide or financial), the irreversible nature of deletion and the potential to disrupt wedding planning workflow by losing important coordination information justifies the Destructive category and high severity.

From the tool's definition The tool description explicitly states "Clear/delete a coordination item by its row number." The verb "delete" indicates irreversible removal of data from the wedding planner spreadsheet.

Questions about delete_coordination

What does the delete_coordination tool do? +

Clear/delete a coordination 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.

How do I enforce a policy on delete_coordination? +

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

What risk level is delete_coordination? +

delete_coordination 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_coordination? +

Yes. Add a rate_limit block to the delete_coordination 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_coordination completely? +

Set action: deny in the PolicyLayer policy for delete_coordination. 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_coordination? +

delete_coordination 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.

// THE FULL RECORD

delete_coordination is one line of Wedding Planner MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.