hubspot_list_deals
AI agents call hubspot_list_deals to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' verb unambiguously indicates a query/retrieval operation that returns deal records from HubSpot without modification. No side effects or data mutation are implied. This matches the Read category definition: retrieves or queries data with no side effects. Confidence is reduced slightly due to empty description, but the tool name provides sufficient evidence for classification.
From the tool's definition Tool name 'hubspot_list_deals' with 'list' verb indicates data retrieval operation. Description is empty, but the naming convention is clear and consistent with read-only list operations seen in sibling tools (airtable_list_bases, airtable_list_records,…
Attacks that exploit this kind of access
hubspot_list_deals. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for hubspot_list_deals: 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_list_deals is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hubspot_list_deals 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_list_deals. 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_list_deals 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 →