Retrieve the law rationale (gerekçe / kanun gerekçesi) from bedesten.adalet.gov.tr. The gerekçe contains: - Purpose and reasoning behind the law (kanunun amacı ve gerekçesi) - Parliamentary committee reports (komisyon raporları) - Article-by-article justifications (madde gerekçeleri) Only availab...
AI agents call get_mevzuat_gerekce to retrieve information from Mevzuat MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs document retrieval from a public legislative database. It allows querying and fetching structured information about Turkish laws but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal — an agent could only retrieve existing legal documents, which are public records. No destructive, financial, or code execution capabilities are present.
From the tool's definition Tool retrieves law rationale documents (kanun gerekçesi) from bedesten.adalet.gov.tr, including purpose, committee reports, and article justifications.
Documented attack patterns abuse exactly the kind of access get_mevzuat_gerekce gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mevzuat MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_mevzuat_gerekce:
{
"version": "1",
"default": "deny",
"tools": {
"get_mevzuat_gerekce": {}
}
}get_mevzuat_gerekce 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.
Retrieve the law rationale (gerekçe / kanun gerekçesi) from bedesten.adalet.gov.tr. The gerekçe contains: - Purpose and reasoning behind the law (kanunun amacı ve gerekçesi) - Parliamentary committee reports (komisyon raporları) - Article-by-article justifications (madde gerekçeleri) Only available for KANUN type legislation that has a published rationale. Not all laws have a gerekçe — check if gerekceId is present in search_mevzuat results. Workflow: search_mevzuat → check gerekceId in results → get_mevzuat_gerekce(gerekceId). It is categorised as a Read tool in the Mevzuat MCP MCP Server, which means it retrieves data without modifying state.
Register the Mevzuat MCP server in PolicyLayer and add a rule for get_mevzuat_gerekce: 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 Mevzuat MCP. Nothing to install.
get_mevzuat_gerekce 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_mevzuat_gerekce 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_mevzuat_gerekce. 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_mevzuat_gerekce is provided by the Mevzuat MCP server (saidsurucu/mevzuat-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Mevzuat MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 Mevzuat MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.