notes_batch_archive
Archive (delete) multiple notes in a single request
This record as markdown: /tools/blacksand-software-hubspot-mcp/notes-batch-archive.md
What notes_batch_archive does on HubSpot MCP
AI agents call notes_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.
Why notes_batch_archive is rated Critical
The tool explicitly performs deletion ('archive (delete)') on multiple notes at once in a batch operation. Archiving in HubSpot is functionally equivalent to deletion and is generally irreversible. The batch nature amplifies the blast radius significantly, making this a high-severity destructive action.
From the tool's definition Archive (delete) multiple notes in a single request
Attacks that exploit this kind of access
The rule that runs notes_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 notes_batch_archive, this is the rule to start with:
notes_batch_archive 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, apply this rule, and every notes_batch_archive call is checked against it from then on.
Questions about notes_batch_archive
Archive (delete) multiple notes 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.
Register the HubSpot MCP server in PolicyLayer and add a rule for notes_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.
notes_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 notes_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 notes_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.
notes_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.
More on HubSpot, and thousands of servers like it.
Across the catalogue