Archive (delete) multiple meetings in a single request
AI agents call meetings_batch_archive 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.
The tool explicitly performs deletion ('archive (delete)') on multiple meetings in batch. Archiving in HubSpot is effectively a soft delete that removes records from active use. The batch nature amplifies the blast radius significantly, as an AI agent could inadvertently delete many meeting records at once, making this Destructive with high severity.
From the tool's definition Archive (delete) multiple meetings in a single request
Attacks that exploit this kind of access
Archive (delete) multiple meetings in a single request. 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 meetings_batch_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 Server. Nothing to install.
meetings_batch_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 meetings_batch_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 meetings_batch_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.
meetings_batch_archive is provided by the HubSpot MCP Server MCP server (kozo93/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →