AI agents use engagement_details_update to create or update resources in HubSpot MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HubSpot MCP environment.
This tool creates or modifies data reversibly by updating engagement records (calls, emails, meetings, notes, etc.) in HubSpot. It does not delete data (which would be Destructive), execute arbitrary code (which would be Execute), or move money (which would be Financial).
From the tool's definition Tool name 'engagement_details_update' and description 'Update an existing engagement' indicate modification of existing data in HubSpot CRM.
Documented attack patterns abuse exactly the kind of access engagement_details_update 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_update:
{
"version": "1",
"default": "deny",
"tools": {
"engagement_details_update": {
"limits": [
{
"counter": "engagement_details_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}engagement_details_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update an existing engagement. It is categorised as a Write tool in the HubSpot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HubSpot MCP server in PolicyLayer and add a rule for engagement_details_update: 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_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the engagement_details_update 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_update. 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_update 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.