Get all engagement activities (calls, emails, meetings, etc.) associated with a deal
AI agents call hubspot_get_engagements_by_deal to retrieve information from HubSpot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical engagement records linked to a deal. It performs a query operation that returns existing data without modifying, creating, deleting, or executing any actions. The blast radius if misused is minimal—an agent accessing this data would at worst retrieve information it shouldn't see, but cannot modify CRM state or trigger external actions. This is a straightforward read operation.
From the tool's definition Tool name includes 'get_' prefix and description states 'Get all engagement activities'. The verb 'Get' combined with retrieving read-only engagement data (calls, emails, meetings) associated with a deal indicates a query operation with no data modification.
Documented attack patterns abuse exactly the kind of access hubspot_get_engagements_by_deal gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HubSpot MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for hubspot_get_engagements_by_deal:
{
"version": "1",
"default": "deny",
"tools": {
"hubspot_get_engagements_by_deal": {}
}
}hubspot_get_engagements_by_deal is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all engagement activities (calls, emails, meetings, etc.) associated with a deal. It is categorised as a Read tool in the HubSpot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HubSpot MCP Server MCP server in PolicyLayer and add a rule for hubspot_get_engagements_by_deal: 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_get_engagements_by_deal is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hubspot_get_engagements_by_deal 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_get_engagements_by_deal. 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_get_engagements_by_deal is provided by the HubSpot MCP Server MCP server (scopiousdigital/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HubSpot MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 HubSpot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.