score_lead
Lead-gen/CRM: rule-based score (0-100) + tier (hot/warm/cold/dead) + conversion probability for one of your leads. Owner-gated. Returns {ok, score, tier, ...}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/score-lead.md
What score_lead does on Gateway
AI agents call score_lead to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | |
secret | string | — | |
lead_id | integer | Yes | the lead to score |
Parameters from the server's own tool schema.
Why score_lead is rated Low
This tool queries and computes metrics on existing lead data without creating, modifying, deleting, or executing external operations. It is a read-only analytical function that retrieves or derives information from CRM records. The owner-gating is an access control mechanism, not a side effect.
From the tool's definition Tool description states it 'Returns {ok, score, tier, ...}' and performs 'rule-based score + tier + conversion probability' calculations on lead data.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs score_lead safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For score_lead, this is the rule to start with:
score_lead 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 Gateway, apply this rule, and every score_lead call is checked against it from then on.
Questions about score_lead
Lead-gen/CRM: rule-based score (0-100) + tier (hot/warm/cold/dead) + conversion probability for one of your leads. Owner-gated. Returns {ok, score, tier, ...}. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
score_lead accepts 3 parameters: handle, secret, lead_id. Required: handle, lead_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for score_lead: 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 Gateway. Nothing to install.
score_lead 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 score_lead 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 score_lead. 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.
score_lead is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue