engagement_details_get

Get details of a specific engagement

SERVERHubSpot MCP SOURCEblacksand-software/hubspot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/blacksand-software-hubspot-mcp/engagement-details-get.md

WHAT IT DOES

What engagement_details_get does on HubSpot MCP

AI agents call engagement_details_get 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.

RISK

Why engagement_details_get is rated Low

This tool retrieves information about a specific engagement record from HubSpot CRM. The verb 'get' combined with 'details' clearly indicates a read-only operation that queries data without side effects. No data is created, modified, deleted, or executed as a result of this tool's use.

From the tool's definition Tool name 'engagement_details_get' and description 'Get details of a specific engagement' indicate retrieval of existing data with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs engagement_details_get 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_get, this is the rule to start with:

engagement_details_get Allowed

engagement_details_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "engagement_details_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect HubSpot MCP, apply this rule, and every engagement_details_get call is checked against it from then on.

FAQ

Questions about engagement_details_get

What does the engagement_details_get tool do? +

Get details of a specific engagement. It is categorised as a Read tool in the HubSpot MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on engagement_details_get? +

Register the HubSpot 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. Nothing to install.

What risk level is engagement_details_get? +

engagement_details_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit engagement_details_get? +

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.

How do I block engagement_details_get completely? +

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.

What MCP server provides engagement_details_get? +

engagement_details_get 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.

KEEP EXPLORING

More on HubSpot, and thousands of servers like it.

This server

All 111 HubSpot tools →

Across the catalogue

get_event_details on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →