crm_score_prospects
Score prospects 0–100 against the workspace ICP rules (agent_settings.icp_rules): country 25, industry 25, employee-in-range 20, any title keyword 30. With no rules configured, every prospect scores 50 (reason no_icp_rules_configured). Returns { scored: [{ id|email, score, matched[], missed[] }] }.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/crm-score-prospects.md
What crm_score_prospects does on Max MCP Server
AI agents call crm_score_prospects 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_score_prospects is rated Low
This is a read-only operation that retrieves and evaluates prospect data against configured rules, returning analytical results. There are no side effects—no prospects are modified, deleted, or acted upon; no external systems are invoked; no financial transactions occur. The tool simply queries workspace settings and prospect attributes to produce a scoring output.
From the tool's definition The tool 'crm_score_prospects' performs a scoring and evaluation operation: it applies ICP rules against prospect data and returns a structured response with scores and matched/missed criteria.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs crm_score_prospects 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_score_prospects, this is the rule to start with:
crm_score_prospects 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_score_prospects call is checked against it from then on.
Questions about crm_score_prospects
Score prospects 0–100 against the workspace ICP rules (agent_settings.icp_rules): country 25, industry 25, employee-in-range 20, any title keyword 30. With no rules configured, every prospect scores 50 (reason no_icp_rules_configured). Returns { scored: [{ id|email, score, matched[], missed[] }] }. 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_score_prospects: 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_score_prospects 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_score_prospects 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_score_prospects. 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_score_prospects 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