Get information about available courts and their document counts
AI agents call list_courts to retrieve information from Entscheidsuche MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries metadata about available courts and aggregates document counts. It is a straightforward informational lookup that does not create, modify, delete, or execute any operations. The minimal blast radius of misuse (returning unwanted but harmless court information) and the clear Read-only nature justify low severity classification.
From the tool's definition Tool name is 'list_courts' with description stating it 'Get[s] information about available courts and their document counts' — purely a retrieval operation with no state modification or side effects.
Attacks that exploit this kind of access
Get information about available courts and their document counts. It is categorised as a Read tool in the Entscheidsuche MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Entscheidsuche MCP Server MCP server in PolicyLayer and add a rule for list_courts: 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 Entscheidsuche MCP Server. Nothing to install.
list_courts 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 list_courts 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 list_courts. 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.
list_courts is provided by the Entscheidsuche MCP Server MCP server (self-tech-labs/entscheidsuche-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →