AI agents call ordinances_get to retrieve information from Legalize without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves legal ordinance data from a GitHub-backed database. It performs a GET-style query operation that reads and returns information without modifying data, triggering external operations, or executing code. The operation is informational and has no destructive or financial implications. A misused call would simply return incorrect or unexpected legal text, presenting minimal risk.
From the tool's definition Tool name 'ordinances_get' and description '자치법규 전문을 조회합니다' (retrieves full text of ordinances). The verb '조회' means 'to query/retrieve/look up', indicating a read-only operation with no modification or execution of side effects.
Documented attack patterns abuse exactly the kind of access ordinances_get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Legalize, and nothing reaches the server without passing your rules. This is the rule we recommend for ordinances_get:
{
"version": "1",
"default": "deny",
"tools": {
"ordinances_get": {}
}
}ordinances_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
자치법규 전문을 조회합니다. It is categorised as a Read tool in the Legalize MCP Server, which means it retrieves data without modifying state.
Register the Legalize MCP server in PolicyLayer and add a rule for ordinances_get: 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 Legalize. Nothing to install.
ordinances_get 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 ordinances_get 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 ordinances_get. 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.
ordinances_get is provided by the Legalize MCP server (legalize-kr/cli-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Legalize, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Legalize tools catalogued and risk-classified — across an index of 43,000+ MCP servers.