crm_update_company
Update an existing company with validated properties
This record as markdown: /tools/blacksand-software-hubspot-mcp/crm-update-company.md
What crm_update_company does on HubSpot MCP
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.
Why crm_update_company is rated Medium
The tool creates or modifies company data in HubSpot's CRM system. This is a classic Write operation: it changes existing records but does not delete them (reversible). Severity is medium because unauthorized company record updates could disrupt business operations, sales pipelines, and data integrity, but the blast radius is limited to a single company record unless batch operations are chained.
From the tool's definition Tool name contains 'update' and description states 'Update an existing company with validated properties' — this modifies data reversibly without deletion.
Attacks that exploit this kind of access
The rule that runs crm_update_company 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 crm_update_company, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect HubSpot MCP, apply this rule, and every crm_update_company call is checked against it from then on.
Questions about crm_update_company
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 (blacksand-software/hubspot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on HubSpot, and thousands of servers like it.
This server
Across the catalogue