crm_batch_delete_associations
Delete multiple associations in a single request
This record as markdown: /tools/blacksand-software-hubspot-mcp/crm-batch-delete-associations.md
What crm_batch_delete_associations does on HubSpot MCP
AI agents call crm_batch_delete_associations to permanently remove resources in HubSpot MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crm_batch_delete_associations is rated Critical
This tool irreversibly removes associations between CRM objects (contacts, companies, deals, etc.). Deletions cannot be undone and represent a loss of data relationships. The batch nature amplifies risk by allowing deletion of many associations in one call. Batch delete operations that cannot be reversed are classified as Destructive per guidelines, which supersedes Write or Execute categories.
From the tool's definition Tool name contains 'delete' and description states it 'Delete multiple associations in a single request'. Batch operation on associations in HubSpot CRM context.
Attacks that exploit this kind of access
The rule that runs crm_batch_delete_associations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and HubSpot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_batch_delete_associations, this is the rule to start with:
crm_batch_delete_associations is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect HubSpot MCP, apply this rule, and every crm_batch_delete_associations call is checked against it from then on.
Questions about crm_batch_delete_associations
Delete multiple associations in a single request. It is categorised as a Destructive tool in the HubSpot MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HubSpot MCP server in PolicyLayer and add a rule for crm_batch_delete_associations: 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 HubSpot MCP. Nothing to install.
crm_batch_delete_associations 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 crm_batch_delete_associations 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 crm_batch_delete_associations. 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.
crm_batch_delete_associations is provided by the HubSpot MCP server (blacksand-software/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on HubSpot, and thousands of servers like it.
Across the catalogue