Get a single contact by ID with specific properties and associations
AI agents call crm_get_contact 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 contact data by ID without modifying, deleting, or executing operations. It is a straightforward read operation typical of CRM data access. The blast radius is minimal—an AI agent misusing this would at worst retrieve unintended contact information, but cannot modify or delete data.
From the tool's definition Tool name 'crm_get_contact' and description 'Get a single contact by ID with specific properties and associations' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access crm_get_contact 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 crm_get_contact:
{
"version": "1",
"default": "deny",
"tools": {
"crm_get_contact": {}
}
}crm_get_contact 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.
Get a single contact by ID with specific properties and associations. 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 crm_get_contact: 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.
crm_get_contact 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 crm_get_contact 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 crm_get_contact. 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.
crm_get_contact 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.