AI agents use update_lead_fields 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 creates or modifies data reversibly by updating lead fields in the LawRuler Legal CRM system. It is clearly a Write operation—it changes existing records but does not delete, execute arbitrary code, or move money.
From the tool's definition Tool name 'update_lead_fields' and description 'Update multiple fields on an existing lead at once' indicate modification of existing data. Accepts custom_fields_json for field updates, which are reversible changes to a CRM record.
Attacks that exploit this kind of access
Update multiple fields on an existing lead at once. custom_fields_json accepts a JSON object of field_name:value pairs for custom fields. 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_fields: 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_fields 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_fields 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_fields. 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_fields 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 →