Search Swiss court decisions AND European Court of Human Rights decisions concerning Switzerland (~2,800 ECHR docs across bge_egmr, hudoc_ch, ecthr_chamber, ecthr_committee, ecthr_grand_chamber) using full-text search. Supports keywords, phrases (in quotes), Boolean operators (AND, OR, NOT), and ...
Risk signalsAccepts freeform code/query input (query) · High parameter count (14 properties)
Part of the Swiss Case Law server.
Free to start. No card required.
AI agents call search_decisions to retrieve information from Swiss Case Law without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_decisions only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"search_decisions": {}
}
}See the full Swiss Case Law policy for all 39 tools.
These attack patterns abuse exactly the kind of access search_decisions gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search Swiss court decisions AND European Court of Human Rights decisions concerning Switzerland (~2,800 ECHR docs across bge_egmr, hudoc_ch, ecthr_chamber, ecthr_committee, ecthr_grand_chamber) using full-text search. Supports keywords, phrases (in quotes), Boolean operators (AND, OR, NOT), and prefix matching (word*). Filter by court, canton, language, date range, chamber, and decision type. Also handles docket number lookup (e.g., 6B_1234/2025) and column-scoped search (regeste:keyword, full_text:keyword). Returns relevance-ranked results enriched with: - court_name (human-readable), court_level, legal_area - statutes: relevant statute articles (e.g. Art. 41 OR) - citation_count: how many decisions cite this one - cited_by_results: how many other results cite this one - is_leading_case: true for highly-cited authoritative decisions Use offset for pagination through large result sets. To find the MOST RECENT decisions: omit the query (or set it empty) and use sort='date_desc' with optional court/canton filters. Example: query='', court='bger', sort='date_desc', limit=5.. It is categorised as a Read tool in the Swiss Case Law MCP Server, which means it retrieves data without modifying state.
Register the Swiss Case Law MCP server in PolicyLayer and add a rule for search_decisions: 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 Swiss Case Law. Nothing to install.
search_decisions 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 search_decisions 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 search_decisions. 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.
search_decisions is provided by the Swiss Case Law MCP server (https://mcp.opencaselaw.ch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 39 Swiss Case Law 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.