delete_property

Delete a custom property in Sanka or a connected CRM for the specified object family. When provider is supplied, the MCP never performs a Sanka-only mutation; omit provider for Sanka properties.

Server Sanka MCP Server sankahq/sanka-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_property does on Sanka MCP Server

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

Why delete_property needs a policy

This tool permanently removes custom properties from Sanka or connected CRMs. Deletion operations cannot be undone and represent irreversible data loss. While the blast radius is somewhat contained (affecting property definitions rather than entire records), the destructive nature and potential for cascading effects (properties used by multiple records/workflows) justify 'high' severity.

From the tool's definition Tool name is 'delete_property' and description states it 'Delete[s] a custom property' with no undo mechanism mentioned. Deletion is irreversible data destruction.

Questions about delete_property

What does the delete_property tool do? +

Delete a custom property in Sanka or a connected CRM for the specified object family. When provider is supplied, the MCP never performs a Sanka-only mutation; omit provider for Sanka properties. It is categorised as a Destructive tool in the Sanka 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_property? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for delete_property: 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 Sanka MCP Server. Nothing to install.

What risk level is delete_property? +

delete_property 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_property? +

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

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

delete_property is provided by the Sanka MCP Server MCP server (sankahq/sanka-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.