AI agents call lawink_precedent_semantic_search 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 queries and retrieves legal precedent data based on semantic similarity. It has no side effects—it does not create, modify, delete, execute code, or trigger external operations. The blast radius of misuse is minimal; an AI agent could retrieve irrelevant or misleading legal precedents but cannot alter the knowledge graph or cause financial/destructive harm. Classified as Read with low severity.
From the tool's definition Tool performs 'semantic search' (의미 검색) on precedents using embeddings; described as 'retrieval' operation on a knowledge graph with no modification or execution capability. The method is passive query-based (공개, 인증 불필요 = public, no authentication needed).
Attacks that exploit this kind of access
판례 시맨틱(의미) 검색 — 임베딩 기반(공개, 인증 불필요). 사안의 의미로. 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_precedent_semantic_search: 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_precedent_semantic_search 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_precedent_semantic_search 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_precedent_semantic_search. 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_precedent_semantic_search 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 →