Track law amendment history with optional article-level diff (법령 개정 추적). Chains: amendment summary → article diff between latest two versions. If article=0, returns only the revision list. If article is specified, also diffs that article between the two most recent revisions. Args: law_name: Law ...
Part of the Korean Law Search server.
Free to start. No card required.
AI agents invoke chain_amendment_track to trigger processes or run actions in Korean Law Search. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
chain_amendment_track can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"chain_amendment_track": {
"limits": [
{
"counter": "chain_amendment_track_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Korean Law Search policy for all 54 tools.
These attack patterns abuse exactly the kind of access chain_amendment_track gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Track law amendment history with optional article-level diff (법령 개정 추적). Chains: amendment summary → article diff between latest two versions. If article=0, returns only the revision list. If article is specified, also diffs that article between the two most recent revisions. Args: law_name: Law name (e.g., "근로기준법") article: Article number to diff (0 = summary only, e.g., 52 for 제52조) date_from: Start date YYYYMMDD (default "20200101") date_to: End date YYYYMMDD (default "20261231") oc: Optional OC override type: Response format Returns: Revision history and optional article diff Examples: >>> chain_amendment_track(law_name="근로기준법") >>> chain_amendment_track(law_name="근로기준법", article=52, date_from="20180101"). It is categorised as a Execute tool in the Korean Law Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Korean Law Search MCP server in PolicyLayer and add a rule for chain_amendment_track: 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 Search. Nothing to install.
chain_amendment_track is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the chain_amendment_track 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 chain_amendment_track. 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.
chain_amendment_track is provided by the Korean Law Search MCP server (rabqatab/lexlink-ko-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 Korean Law Search tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.