This record as markdown: /tools/io-github-alifanov-scopegate/hubspot-get-deal.md
What hubspot_get_deal does on ScopeGate
AI agents call hubspot_get_deal to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hubspot_get_deal is rated Low
This tool retrieves a single deal record from HubSpot by its identifier. It queries existing data without modifying, creating, or deleting any records. This is a straightforward read operation with minimal blast radius—an agent misusing this would only access deal information visible in the HubSpot instance, not alter or delete it.
From the tool's definition Tool name is 'hubspot_get_deal' and description states 'Get a deal by ID'. The verb 'get' and lack of mutation language (create, update, delete) indicate retrieval-only operation.
Attacks that exploit this kind of access
The rule that runs hubspot_get_deal safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hubspot_get_deal, this is the rule to start with:
hubspot_get_deal 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 ScopeGate, apply this rule, and every hubspot_get_deal call is checked against it from then on.
Questions about hubspot_get_deal
Get a deal by ID. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for hubspot_get_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 ScopeGate. Nothing to install.
hubspot_get_deal 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_get_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_get_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_get_deal is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue