Create a new company in HubSpot CRM
AI agents use create_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 creates new records in HubSpot's CRM database. While creation is reversible (the company record can be updated or removed), this represents a Write category action—data modification without permanent destruction. Severity is medium because misuse could pollute the CRM with fake/unwanted company records, but the impact is scoped to CRM data and reversible.
From the tool's definition Tool name 'create_company' and description 'Create a new company in HubSpot CRM' explicitly indicate data creation. This is a reversible write operation (companies can be modified or deleted later).
Attacks that exploit this kind of access
Create a new company in HubSpot CRM. 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 create_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.
create_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 create_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 create_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.
create_company is provided by the HubSpot MCP Server MCP server (sanketskasar/hubspot-mcp-server). 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 →