engagement_details_list
List all engagements with optional filtering
This record as markdown: /tools/blacksand-software-hubspot-mcp/engagement-details-list.md
What engagement_details_list does on HubSpot MCP
AI agents call engagement_details_list to retrieve information from HubSpot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why engagement_details_list is rated Low
This tool retrieves and queries engagement records from HubSpot CRM with optional filters. It has no side effects—it does not create, modify, delete, or execute operations. The blast radius of misuse is minimal; an agent could retrieve sensitive engagement data but cannot alter or delete it. Classified as Read with low severity.
From the tool's definition Tool name 'engagement_details_list' and description 'List all engagements with optional filtering' indicate data retrieval without modification. No destructive, write, execute, or financial operations are implied.
Attacks that exploit this kind of access
The rule that runs engagement_details_list 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 engagement_details_list, this is the rule to start with:
engagement_details_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect HubSpot MCP, apply this rule, and every engagement_details_list call is checked against it from then on.
Questions about engagement_details_list
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 (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.
This server
Across the catalogue