update_lead · Revenue Engine MCP: Risk & Policy

WHAT IT DOES

What update_lead does on Revenue Engine MCP

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

WHY IT NEEDS A POLICY

Why update_lead needs a policy

This tool modifies existing lead records, which is a reversible Write operation. Severity is high because leads are critical business assets in a revenue tracking system, and unauthorized updates could corrupt sales pipeline data, misrepresent prospect status, or trigger incorrect business decisions. However, it is not Destructive since updates are reversible, and not Financial since it doesn't directly move money.

From the tool's definition Tool name 'update_lead' and description 'Update an existing lead' indicate modification of existing data in the lead pipeline. The server context shows this is part of lead pipeline management within a revenue tracking system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_lead Rate-limited

update_lead 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": {
      "limits": [
        {
          "counter": "update_lead_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Revenue Engine MCP, so you can run agents against it safely.

FAQ

Questions about update_lead

What does the update_lead tool do? +

Update an existing lead. It is categorised as a Write tool in the Revenue Engine MCP 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? +

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

What risk level is update_lead? +

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

Can I rate-limit update_lead? +

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

How do I block update_lead completely? +

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

What MCP server provides update_lead? +

update_lead is provided by the Revenue Engine MCP server (promptishoperations/mcpspec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.