delete_association

Delete an association between two Sanka records. Prefer association_id; otherwise pass source_object/source_id, target_object/target_id, and label_id or label.

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

What delete_association does on Sanka MCP Server

AI agents call delete_association 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_association needs a policy

This tool performs an irreversible deletion operation on data associations. Although it deletes a relationship rather than the records themselves, the deletion cannot be undone and represents a destructive action. The severity is high because misconfiguration or misuse could break critical data relationships in a business system, potentially affecting workflows, reporting, and data integrity.

From the tool's definition The tool name explicitly contains 'delete' and the description states it 'Delete an association between two Sanka records.' The action is irreversible and removes data relationships.

Questions about delete_association

What does the delete_association tool do? +

Delete an association between two Sanka records. Prefer association_id; otherwise pass source_object/source_id, target_object/target_id, and label_id or label. 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_association? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for delete_association: 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_association? +

delete_association 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_association? +

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

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

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