AI agents use update_lead_status 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.
This tool modifies lead records by changing their status field, which is a Write operation (creates or modifies data reversibly). The change is not destructive since status can be updated back to a previous value. Severity is medium because incorrect status changes could disrupt lead workflows and case management, but the effect is limited to a single lead's metadata and is easily reversible.
From the tool's definition Tool name 'update_lead_status' and description 'Update the status of a lead/intake' indicate modification of existing lead data. Status updates are reversible changes to CRM records.
Attacks that exploit this kind of access
Update the status of a lead/intake. 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.
Register the Lawruler 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 Lawruler. Nothing to install.
update_lead_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
update_lead_status 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →