engagement_details_delete

Delete an engagement

SERVERHubSpot MCP SOURCEblacksand-software/hubspot-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about engagement_details_delete

What does the engagement_details_delete tool do? +

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.

How do I enforce a policy on engagement_details_delete? +

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.

What risk level is engagement_details_delete? +

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.

Can I rate-limit engagement_details_delete? +

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.

How do I block engagement_details_delete completely? +

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.

What MCP server provides engagement_details_delete? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of HubSpot's. Pull the full record:

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.