Update an existing company with validated properties
AI agents use crm_update_company 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 modifies company records in HubSpot's CRM system. While the changes are reversible (making it Write rather than Destructive), the blast radius is significant because companies are core business entities whose incorrect modification could disrupt sales pipelines, customer relationships, and business operations.
From the tool's definition Tool name 'crm_update_company' and description 'Update an existing company with validated properties' indicate modification of existing CRM data in HubSpot.
Documented attack patterns abuse exactly the kind of access crm_update_company 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_update_company:
{
"version": "1",
"default": "deny",
"tools": {
"crm_update_company": {
"limits": [
{
"counter": "crm_update_company_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}crm_update_company 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 company with validated properties. 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 crm_update_company: 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_update_company 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 crm_update_company 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_update_company. 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_update_company 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.