meetings_batch_archive

Archive (delete) multiple meetings in a single request

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/meetings-batch-archive.md

WHAT IT DOES

What meetings_batch_archive does on HubSpot MCP

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

RISK

Why meetings_batch_archive is rated Critical

The tool explicitly performs deletion ('archive/delete') on multiple meetings at once in a batch operation. Batch deletion amplifies the blast radius significantly as many records can be removed in a single call, making this irreversible at scale.

From the tool's definition Archive (delete) multiple meetings in a single request

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs meetings_batch_archive safely

PolicyLayer is an MCP gateway: it sits between your AI agents and HubSpot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For meetings_batch_archive, this is the rule to start with:

meetings_batch_archive Hidden

meetings_batch_archive is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "meetings_batch_archive"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect HubSpot MCP, apply this rule, and every meetings_batch_archive call is checked against it from then on.

FAQ

Questions about meetings_batch_archive

What does the meetings_batch_archive tool do? +

Archive (delete) multiple meetings in a single request. 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 meetings_batch_archive? +

Register the HubSpot 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. Nothing to install.

What risk level is meetings_batch_archive? +

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.

Can I rate-limit meetings_batch_archive? +

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.

How do I block meetings_batch_archive completely? +

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.

What MCP server provides meetings_batch_archive? +

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

KEEP EXPLORING

More on HubSpot, and thousands of servers like it.

This server

All 111 HubSpot tools → Critical-risk tools on this server →

Across the catalogue

archive_purge on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →