This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/hubspot-list-deals.md
What hubspot_list_deals does on UnClick
AI agents call hubspot_list_deals to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
after | string | — | Pagination cursor from a previous response |
limit | number | — | Deals to return (max 100, default 25) |
properties | string | — | Comma-separated properties to return |
access_token | string | Yes | HubSpot Private App access token |
Parameters from the server's own tool schema.
Why hubspot_list_deals is rated Low
This tool retrieves or queries existing deal records from HubSpot's CRM system. The verb 'list' and the absence of any mutation language (create, update, delete, modify) indicate a read-only operation. The data returned may contain business-sensitive information (deal stages, values, contacts), but the tool itself has no side effects—it does not create, modify, or delete deals.
From the tool's definition Tool name and description indicate a list/query operation: 'List HubSpot CRM deals' retrieves deal data with no modification capability.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs hubspot_list_deals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hubspot_list_deals, this is the rule to start with:
hubspot_list_deals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every hubspot_list_deals call is checked against it from then on.
Questions about hubspot_list_deals
List HubSpot CRM deals. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hubspot_list_deals accepts 4 parameters: after, limit, properties, access_token. Required: access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue