Critical Risk →

engagement_details_archive

Archive (delete) an engagement

How to control engagement_details_archive ↓

AI agents call engagement_details_archive 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.

Critical Risk

The tool explicitly archives/deletes an engagement record in HubSpot CRM. Archive operations in HubSpot are typically soft-deletes but are considered destructive as they remove data from active access. The description confirms this is a deletion operation, making it Destructive.

From the tool's definition Archive (delete) an engagement

Documented attack patterns abuse exactly the kind of access engagement_details_archive gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and HubSpot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for engagement_details_archive:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "engagement_details_archive"
  ]
}

engagement_details_archive disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register HubSpot MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the engagement_details_archive tool do? +

Archive (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_archive? +

Register the HubSpot MCP server in PolicyLayer and add a rule for engagement_details_archive: 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_archive? +

engagement_details_archive 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_archive? +

Yes. Add a rate_limit block to the engagement_details_archive 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_archive completely? +

Set action: deny in the PolicyLayer policy for engagement_details_archive. 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_archive? +

engagement_details_archive is provided by the HubSpot MCP server (shinzo-labs/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every HubSpot MCP tool call.

Deterministic rules across all 112 HubSpot MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

112 HubSpot MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.