This record as markdown: /tools/blacksand-software-hubspot-mcp/meetings-delete.md
What meetings_delete does on HubSpot MCP
AI agents call meetings_delete 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 meetings_delete is rated Critical
This tool permanently removes meeting records from the HubSpot CRM, which cannot be undone. Deletion is irreversible data loss, placing it in the Destructive category. Severity is high because an AI agent misusing this could permanently erase important business records (customer meetings, engagement history), affecting business operations and compliance.
From the tool's definition Tool name is 'meetings_delete' with description 'Delete a meeting'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs meetings_delete 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_delete, this is the rule to start with:
meetings_delete 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 meetings_delete call is checked against it from then on.
Questions about meetings_delete
Delete a meeting. 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 meetings_delete: 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.
meetings_delete 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_delete 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_delete. 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_delete 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