AI agents call calls_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.
The tool explicitly archives/deletes a call record. In HubSpot, archiving is effectively a soft-delete that removes the record from active use. The description uses both 'archive' and 'delete', indicating irreversible removal of CRM data. Misuse could result in permanent loss of call history records across the CRM.
From the tool's definition Archive (delete) a call record
Documented attack patterns abuse exactly the kind of access calls_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 calls_archive:
{
"version": "1",
"default": "deny",
"hide": [
"calls_archive"
]
}calls_archive disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Archive (delete) a call record. 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 calls_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.
calls_archive 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 calls_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.
Set action: deny in the PolicyLayer policy for calls_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.
calls_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.
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.