This record as markdown: /tools/blacksand-software-hubspot-mcp/crm-delete-object.md
What crm_delete_object does on HubSpot MCP
AI agents call crm_delete_object 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_delete_object is rated Critical
This tool performs deletion of CRM objects (contacts, companies, deals, leads, or engagements), which is an irreversible operation that cannot be undone. Unauthorized or accidental deletion could permanently remove critical customer relationship data. This is the most severe category applicable and warrants critical severity due to the potential for significant data loss in a business-critical system.
From the tool's definition Tool name 'crm_delete_object' with description 'Delete a CRM object' indicates irreversible deletion of data from HubSpot CRM.
Attacks that exploit this kind of access
The rule that runs crm_delete_object 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_delete_object, this is the rule to start with:
crm_delete_object 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_delete_object call is checked against it from then on.
Questions about crm_delete_object
Delete a CRM object. 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_delete_object: 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_delete_object 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_delete_object 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_delete_object. 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_delete_object 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