Update an existing company with validated properties
AI agents use crm_update_company to create or update resources in HubSpot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HubSpot MCP Server environment.
The tool modifies existing company records in HubSpot's CRM system. This is a Write operation (reversible data modification), not Destructive, since updates can be undone or corrected. Severity is medium because erroneous bulk updates could impact business relationships and reporting, but the effect is limited to a single company entity unless combined with batch operations.
From the tool's definition Tool name contains 'update' and description states 'Update an existing company with validated properties', indicating reversible modification of CRM data.
Attacks that exploit this kind of access
Update an existing company with validated properties. It is categorised as a Write tool in the HubSpot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HubSpot MCP Server 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 Server. 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 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 →