Get details of a specific engagement
AI agents call engagement_details_get 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 engagement information from HubSpot's CRM without creating, modifying, deleting, or executing any operations. It is a simple data query operation with no side effects or blast radius if misused by an AI agent.
From the tool's definition Tool name 'engagement_details_get' and description 'Get details of a specific engagement' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get details of a specific engagement. 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 engagement_details_get: 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.
engagement_details_get 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_get 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_get. 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_get is provided by the HubSpot MCP Server MCP server (kozo93/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →