Low Risk

hs_get_deal

Fetch a deal's full details by ID. Returns deal name, amount, stage, owner, and linked contacts and companies.

Part of the Hubspot server.

hs_get_deal is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE HUBSPOT →

Free to start. No card required.

AI agents call hs_get_deal to retrieve information from Hubspot without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though hs_get_deal only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "hs_get_deal": {}
  }
}

See the full Hubspot policy for all 27 tools.

Get this rule live on your own Hubspot server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY HUBSPOT →

View all 27 tools →

These attack patterns abuse exactly the kind of access hs_get_deal gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so hs_get_deal only ever does what you allow.

SECURE HUBSPOT →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the hs_get_deal tool do? +

Fetch a deal's full details by ID. Returns deal name, amount, stage, owner, and linked contacts and companies.. It is categorised as a Read tool in the Hubspot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hs_get_deal? +

Register the Hubspot MCP server in PolicyLayer and add a rule for hs_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 Hubspot. Nothing to install.

What risk level is hs_get_deal? +

hs_get_deal is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hs_get_deal? +

Yes. Add a rate_limit block to the hs_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.

How do I block hs_get_deal completely? +

Set action: deny in the PolicyLayer policy for hs_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.

What MCP server provides hs_get_deal? +

hs_get_deal is provided by the Hubspot MCP server (https://gateway.pipeworx.io/hubspot/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hubspot tool call.

Deterministic rules across all 27 Hubspot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.