crm_pipeline_risk_scan
Scan open HubSpot deals for risk: days inactive, days-to-close, missing fields (amount/owner/next_step/last_activity), close-date slipping, and high-value-low-activity. Computes a transparent weighted risk_score (0–100) and a PRIVATE suggested nudge draft to the owner (never sent). Uses agent_set...
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/crm-pipeline-risk-scan.md
What crm_pipeline_risk_scan does on Max MCP Server
AI agents call crm_pipeline_risk_scan 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.
Why crm_pipeline_risk_scan is rated Low
This tool queries and analyzes HubSpot deal data to compute risk scores and generate internal draft suggestions. It performs no modifications to the CRM, sends no messages, executes no external operations, and creates no financial or destructive side effects. The suggested nudge draft is explicitly marked as PRIVATE and never sent, confirming it is a read-only analysis operation.
From the tool's definition Tool description explicitly states it 'Scan[s]' deals and 'Returns { scanned_count, flagged:[...] }'. The phrase 'never sent' confirms no autonomous writes or actions are performed. Only retrieves and analyzes existing CRM data.
Attacks that exploit this kind of access
The rule that runs crm_pipeline_risk_scan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_pipeline_risk_scan, this is the rule to start with:
crm_pipeline_risk_scan 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 Max MCP Server, apply this rule, and every crm_pipeline_risk_scan call is checked against it from then on.
Questions about crm_pipeline_risk_scan
Scan open HubSpot deals for risk: days inactive, days-to-close, missing fields (amount/owner/next_step/last_activity), close-date slipping, and high-value-low-activity. Computes a transparent weighted risk_score (0–100) and a PRIVATE suggested nudge draft to the owner (never sent). Uses agent_settings.risk_thresholds. Returns { scanned_count, flagged:[...] }. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for crm_pipeline_risk_scan: 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 Max MCP Server. Nothing to install.
crm_pipeline_risk_scan 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 crm_pipeline_risk_scan 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 crm_pipeline_risk_scan. 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.
crm_pipeline_risk_scan is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue