set_lead_status

Move a lead along the pipeline (new/contacted/qualified/won/lost). Records the update time.

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/set-lead-status.md

WHAT IT DOES

What set_lead_status does on FeatureBoard

AI agents use set_lead_status to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.

RISK

Why set_lead_status is rated Medium

This tool modifies the status field of a lead record in a CRM-like system, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool name 'set_lead_status' and description 'Move a lead along the pipeline (new/contacted/qualified/won/lost). Records the update time.' indicate modification of existing lead data through state transitions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_lead_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_lead_status, this is the rule to start with:

set_lead_status Rate-limited

set_lead_status stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_lead_status": {
      "limits": [
        {
          "counter": "set_lead_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every set_lead_status call is checked against it from then on.

FAQ

Questions about set_lead_status

What does the set_lead_status tool do? +

Move a lead along the pipeline (new/contacted/qualified/won/lost). Records the update time. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_lead_status? +

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

What risk level is set_lead_status? +

set_lead_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_lead_status? +

Yes. Add a rate_limit block to the set_lead_status 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 set_lead_status completely? +

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

set_lead_status is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →