engagement_details_delete
Delete an engagement
This record as markdown: /tools/blacksand-software-hubspot-mcp/engagement-details-delete.md
What engagement_details_delete does on HubSpot MCP
AI agents call engagement_details_delete 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 engagement_details_delete is rated Critical
This tool permanently removes engagement records from HubSpot without the possibility of reversal. Engagements are critical business data representing customer interactions. Unauthorized or accidental deletion could cause significant data loss, audit trail corruption, and business disruption.
From the tool's definition Tool name 'engagement_details_delete' explicitly performs deletion operation. Description states 'Delete an engagement', which is an irreversible data destruction action on CRM engagement records (calls, emails, meetings, notes, tasks).
Attacks that exploit this kind of access
The rule that runs engagement_details_delete 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 engagement_details_delete, this is the rule to start with:
engagement_details_delete 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 engagement_details_delete call is checked against it from then on.
Questions about engagement_details_delete
Delete an engagement. 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 engagement_details_delete: 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.
engagement_details_delete 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 engagement_details_delete 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 engagement_details_delete. 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.
engagement_details_delete 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