AI agents call get_lead to retrieve information from Lawruler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing lead/intake information from the CRM database without creating, modifying, deleting, or executing any side effects. It is a simple data retrieval operation. Severity is low because unauthorized read access to lead contact information in a legal CRM could expose PII, but the tool itself has no capability to cause irreversible harm, execute code, or move money.
From the tool's definition Tool name and description: 'Retrieve a lead/intake by LeadID. Returns contact info, status, case type, and all stored fields.' The verb 'Retrieve' and the action of returning data with no modification capability clearly indicate a read-only operation.
Attacks that exploit this kind of access
Retrieve a lead/intake by LeadID. Returns contact info, status, case type, and all stored fields. It is categorised as a Read tool in the Lawruler MCP Server, which means it retrieves data without modifying state.
Register the Lawruler MCP server in PolicyLayer and add a rule for get_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 Lawruler. Nothing to install.
get_lead is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_lead 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 →