hubspot_delete_meeting
Archive (soft delete) a meeting engagement in HubSpot.
This record as markdown: /tools/adeel0x01-hubspot-mcp-tools/hubspot-delete-meeting.md
What hubspot_delete_meeting does on HubSpot MCP Server
AI agents call hubspot_delete_meeting 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.
Why hubspot_delete_meeting is rated Critical
Although described as a 'soft delete' (archive), this tool irreversibly removes meeting engagement data from HubSpot. Even soft deletes prevent normal access to the data and represent a destructive action. Given the context of sibling tools that create and update records, this delete operation has the potential for significant data loss if misused by an AI agent.
From the tool's definition Tool name is 'hubspot_delete_meeting' and description states it 'Archive (soft delete) a meeting engagement in HubSpot.' The operation removes/deletes meeting records from the CRM, which cannot be easily undone by an AI agent.
Attacks that exploit this kind of access
The rule that runs hubspot_delete_meeting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and HubSpot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hubspot_delete_meeting, this is the rule to start with:
hubspot_delete_meeting 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 Server, apply this rule, and every hubspot_delete_meeting call is checked against it from then on.
Questions about hubspot_delete_meeting
Archive (soft delete) a meeting engagement in HubSpot. 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 hubspot_delete_meeting: 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.
hubspot_delete_meeting 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 hubspot_delete_meeting 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 hubspot_delete_meeting. 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.
hubspot_delete_meeting is provided by the HubSpot MCP Server MCP server (adeel0x01/hubspot-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on HubSpot MCP Server, and thousands of servers like it.
Across the catalogue