AI agents call lawink_statute_by_precedent to retrieve information from Lawink without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries legal statutes and their relations to precedents—a read-only information lookup operation. It has no side effects, does not modify data, execute code, delete records, or involve financial transactions. The Korean text confirms it outputs legal statute information (도출 = derive/extract) based on precedent input, which is purely informational retrieval.
From the tool's definition Tool name 'lawink_statute_by_precedent' and description indicate it 'derives legal statutes from cases/precedents' (사안 → 근거 법령 도출). The description explicitly states this is a lawyer's basic entry point tool for retrieving applicable legal statutes.
Attacks that exploit this kind of access
★★사안 → 근거 법령 도출 (변호사용 기본·1차 진입점). 근거 조문이 필요하면 이 도구를. It is categorised as a Read tool in the Lawink MCP Server, which means it retrieves data without modifying state.
Register the Lawink MCP server in PolicyLayer and add a rule for lawink_statute_by_precedent: 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 Lawink. Nothing to install.
lawink_statute_by_precedent 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 lawink_statute_by_precedent 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 lawink_statute_by_precedent. 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.
lawink_statute_by_precedent is provided by the Lawink MCP server (ntriq/lawink-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 →