hubspot_delete_email_engagement
Archive (soft delete) an email engagement in HubSpot.
This record as markdown: /tools/adeel0x01-hubspot-mcp-tools/hubspot-delete-email-engagement.md
What hubspot_delete_email_engagement does on HubSpot MCP Server
AI agents call hubspot_delete_email_engagement to permanently remove resources in HubSpot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why hubspot_delete_email_engagement is rated Critical
Although described as 'soft delete' (archived rather than hard purged), deleting email engagements irreversibly removes them from normal CRM operations. An AI agent misusing this tool could systematically erase critical communication records, deal history, or engagement data that cannot be easily restored. This exceeds Write (reversible modifications) because archives cannot be undone by standard users.
From the tool's definition Tool name contains 'delete' and description states 'Archive (soft delete) an email engagement'. Soft delete is still an irreversible removal of data from the user's normal workflow, preventing recovery without admin intervention.
Attacks that exploit this kind of access
The rule that runs hubspot_delete_email_engagement safely
PolicyLayer is an MCP gateway: it sits between your AI agents and HubSpot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hubspot_delete_email_engagement, this is the rule to start with:
hubspot_delete_email_engagement 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 Server, apply this rule, and every hubspot_delete_email_engagement call is checked against it from then on.
Questions about hubspot_delete_email_engagement
Archive (soft delete) an email engagement in HubSpot. It is categorised as a Destructive tool in the HubSpot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HubSpot MCP Server MCP server in PolicyLayer and add a rule for hubspot_delete_email_engagement: 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 Server. Nothing to install.
hubspot_delete_email_engagement 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 hubspot_delete_email_engagement 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 hubspot_delete_email_engagement. 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.
hubspot_delete_email_engagement is provided by the HubSpot MCP Server MCP server (adeel0x01/hubspot-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on HubSpot MCP Server, and thousands of servers like it.
Across the catalogue