# crm_get_deal

Fetch a single HubSpot deal by id, including its full properties and associated company/contact ids. Returns null if not found.

Agent View of the PolicyLayer registry record for `crm_get_deal`. HTML page: https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/crm-get-deal

## Facts

- Tool: `crm_get_deal`
- Server: Max MCP Server (`digital-crew-technologies/max-mcp-server`) — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server.md
- Homepage: https://github.com/Digital-Crew-Technologies/max-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "crm_get_deal",
    "arguments": {}
  }
}
```

## Why crm_get_deal is rated Low

This tool performs a read-only operation that queries a CRM system for deal information. It has no capability to modify, delete, or execute actions—it only retrieves existing data. The blast radius of misuse is low, as unauthorized reads of deal data, while potentially sensitive, do not cause irreversible damage or enable further destructive actions without additional tools.

From the tool's own definition: "'Fetch a single HubSpot deal by id' — the tool retrieves data without modifying it. The description explicitly uses 'Fetch' and 'Returns', indicating a query operation with no side effects."

## Use case

AI agents call crm_get_deal to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Max MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crm_get_deal": {}
  }
}
```

## Other tools on Max MCP Server (414)

- `automation_cancel_run` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-cancel-run.md
- `automation_delete` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-delete.md
- `automation_discard_draft` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-discard-draft.md
- `bulk_delete_organizations` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/bulk-delete-organizations.md
- `bulk_delete_prospects` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/bulk-delete-prospects.md
- `cancel_meeting` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-meeting.md
- `cancel_meeting_series` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-meeting-series.md
- `cancel_warmup` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-warmup.md
- `clear_failed_requests` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/clear-failed-requests.md
- `decline_meeting` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/decline-meeting.md
- `delete_calendar_event` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-calendar-event.md
- `delete_campaign` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-campaign.md
- `delete_campaign_attachment` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-campaign-attachment.md
- `delete_deal` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal.md
- `delete_deal_attachment` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-attachment.md
- `delete_deal_pipeline` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-pipeline.md
- `delete_deal_stage` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-stage.md
- `delete_deal_stage_rule` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-stage-rule.md
- `delete_icp` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-icp.md
- `delete_meeting_link` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-meeting-link.md
- `delete_organization` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-organization.md
- `delete_prospect` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect.md
- `delete_prospect_list` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect-list.md
- `delete_prospect_profile_hook` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect-profile-hook.md
- `delete_saved_view` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-saved-view.md
- `delete_schedule_preset` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-schedule-preset.md
- `disconnect_data_supplier` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/disconnect-data-supplier.md
- `pipeline_delete_campaign_route` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-campaign-route.md
- `pipeline_delete_canvas_draft` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-canvas-draft.md
- `pipeline_delete_link` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-link.md
- …and 384 more: https://policylayer.com/tools/digital-crew-technologies-max-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=digital-crew-technologies-max-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/digital-crew-technologies-max-mcp-server
