get_article_history
AI agents call get_article_history to retrieve information from Korean Law MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical versions or legislative progression of legal articles—a read operation with no side effects, no data modification, and no external execution. It queries the National Law Information Center API to fetch historical records, consistent with the server's search and retrieval mandate.
From the tool's definition Tool name 'get_article_history' and server purpose show this retrieves legislative history and precedent data. Server description states 'legislative history tracking' as a core feature.
Attacks that exploit this kind of access
get_article_history. It is categorised as a Read tool in the Korean Law MCP MCP Server, which means it retrieves data without modifying state.
Register the Korean Law MCP server in PolicyLayer and add a rule for get_article_history: 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 Korean Law MCP. Nothing to install.
get_article_history 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_article_history 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_article_history. 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_article_history is provided by the Korean Law MCP server (seo-jinseok/korean-law-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 →