hubspot_create_deal
AI agents use hubspot_create_deal to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
Creating a deal in HubSpot is a reversible data modification operation (deals can be updated or archived). It does not delete data (Destructive), execute arbitrary code (Execute), move money directly (Financial—though deals may eventually lead to financial transactions, deal creation itself is a CRM record operation), or trigger irreversible consequences.
From the tool's definition Tool name 'hubspot_create_deal' indicates creation of a deal record in HubSpot CRM, following the pattern of other Write operations visible on this server (airtable_create_record). The description is empty, limiting direct confirmation.
Attacks that exploit this kind of access
hubspot_create_deal. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for hubspot_create_deal: 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 Integrations MCP. Nothing to install.
hubspot_create_deal 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 hubspot_create_deal 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 hubspot_create_deal. 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.
hubspot_create_deal is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →