Search Austrian court decisions (Judikatur). Use this tool to find court decisions from Austrian courts. Example: gericht=
AI agents call ris_judikatur to retrieve information from RIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available court decision documents from Austria's official legal database. It has no side effects—it does not create, modify, delete, execute code, or commit financial transactions. The search/find functionality is read-only data access, making it a Read category tool with low severity risk.
From the tool's definition Tool description explicitly states 'Search Austrian court decisions' and 'find court decisions from Austrian courts'. The verb 'search' and 'find' indicate data retrieval with no modification capability.
Documented attack patterns abuse exactly the kind of access ris_judikatur gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ris_judikatur:
{
"version": "1",
"default": "deny",
"tools": {
"ris_judikatur": {}
}
} ris_judikatur 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.
Search Austrian court decisions (Judikatur). Use this tool to find court decisions from Austrian courts. Example: gericht=. It is categorised as a Read tool in the RIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RIS MCP Server MCP server in PolicyLayer and add a rule for ris_judikatur: 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 RIS MCP Server. Nothing to install.
ris_judikatur 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 ris_judikatur 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 ris_judikatur. 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.
ris_judikatur is provided by the RIS MCP Server MCP server (honeyfield-org/ris-mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RIS MCP Server, 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.
12 RIS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.