AI agents use update_lead_owner 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 metadata about a lead (reassigns ownership) but does not create, delete, or execute external operations. It is reversible — ownership can be reassigned again. The blast radius is moderate: incorrect assignment could misdirect client matters, delay response times, or create billing confusion, but the action is not destructive or financial.
From the tool's definition Tool description states 'Set the owner of a lead/intake' — a modifying action that changes the assigned attorney/partner ownership of a legal matter. This is a reversible update operation.
Attacks that exploit this kind of access
Set the owner of a lead/intake (LeadOwner — the attorney or partner who owns the matter). 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_owner: 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_owner 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_owner 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_owner. 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_owner 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 →