AI agents call engagement_details_list to retrieve information from HubSpot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries engagement data from HubSpot with no ability to modify, delete, or execute operations. The filtering capability is a standard read-operation parameter. Listing data with filters is a classic Read operation with minimal risk—the worst case is information disclosure of existing CRM records, which has low blast radius compared to modification or deletion.
From the tool's definition Tool is named 'engagement_details_list' and described as 'List all engagements with optional filtering'. The verb 'list' combined with 'optional filtering' indicates data retrieval without modification.
Documented attack patterns abuse exactly the kind of access engagement_details_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HubSpot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for engagement_details_list:
{
"version": "1",
"default": "deny",
"tools": {
"engagement_details_list": {}
}
}engagement_details_list 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.
List all engagements with optional filtering. It is categorised as a Read tool in the HubSpot MCP MCP Server, which means it retrieves data without modifying state.
Register the HubSpot MCP server in PolicyLayer and add a rule for engagement_details_list: 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.
engagement_details_list 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 engagement_details_list 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 engagement_details_list. 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.
engagement_details_list is provided by the HubSpot MCP server (shinzo-labs/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 112 HubSpot MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
112 HubSpot MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.