update_lead_assignee · Lawruler MCP: Risk & Policy

WHAT IT DOES

What update_lead_assignee does on Lawruler

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

WHY IT NEEDS A POLICY

Why update_lead_assignee needs a policy

This tool modifies metadata (assignee) on existing leads—a classic Write operation. The modification is reversible (can reassign to another staff member). Severity is medium because misassignment could cause leads to be routed to wrong staff, potentially causing missed deadlines or disclosure of sensitive client information, but the operation itself does not destroy data or move money.

From the tool's definition Tool updates lead assignment to a staff member; modifies existing lead data via 'LeadAssignee' field without deleting or destroying records. Description states 'Assign a lead/intake to a staff member', which is a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_lead_assignee Rate-limited

update_lead_assignee 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_assignee": {
      "limits": [
        {
          "counter": "update_lead_assignee_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 Lawruler, so you can run agents against it safely.

FAQ

Questions about update_lead_assignee

What does the update_lead_assignee tool do? +

Assign a lead/intake to a staff member (LeadAssignee — the user managing the lead). It is categorised as a Write tool in the Lawruler 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_assignee? +

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

What risk level is update_lead_assignee? +

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

Can I rate-limit update_lead_assignee? +

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

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

update_lead_assignee is provided by the Lawruler MCP server (rosenadvertising/lawruler-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.