Get recent engagement activities across all contacts and companies
AI agents call hubspot_get_recent_engagements 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 queries and retrieves engagement activity history from HubSpot CRM. The 'get' verb and retrieval-focused description indicate a read-only operation that accesses existing data without creating, modifying, or deleting records. While engagement data may be sensitive business information, the lack of side effects and the read-only nature classify this as a Read category tool with low severity.
From the tool's definition Tool name contains 'get' and description states 'Get recent engagement activities' - retrieves data with no modification, deletion, or side effects.
Documented attack patterns abuse exactly the kind of access hubspot_get_recent_engagements 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_recent_engagements:
{
"version": "1",
"default": "deny",
"tools": {
"hubspot_get_recent_engagements": {}
}
} hubspot_get_recent_engagements 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 recent engagement activities across all contacts and companies. 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_recent_engagements: 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_recent_engagements 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_recent_engagements 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_recent_engagements. 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_recent_engagements is provided by the HubSpot MCP Server MCP server (lkm1developer/hubspot-mcp-server). 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.
8 HubSpot MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.