update_lead_status

Update a lead

SERVERBusinys SOURCE@businys/mcp-server

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/app-businys-mcp-server/update-lead-status.md

WHAT IT DOES

What update_lead_status does on Businys

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

RISK

Why update_lead_status is rated Medium

Updating a lead status changes business-critical customer relationship data but is reversible (status can be changed again). This is squarely in the Write category rather than Read (no retrieval only), Execute (no code/command execution), Destructive (reversible), or Financial (no money movement).

From the tool's definition Tool name 'update_lead_status' and description 'Update a lead' indicate modification of existing lead data. The verb 'update' is a classic Write operation that creates or modifies data reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_lead_status safely

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

update_lead_status Rate-limited

update_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": {
    "update_lead_status": {
      "limits": [
        {
          "counter": "update_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 Businys, apply this rule, and every update_lead_status call is checked against it from then on.

FAQ

Questions about update_lead_status

What does the update_lead_status tool do? +

Update a lead. It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_lead_status? +

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

What risk level is update_lead_status? +

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

Can I rate-limit update_lead_status? +

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

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

update_lead_status is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Businys, and thousands of servers like it.

This server

All 248 Businys tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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