Low Risk

judgment_get_header

Get metadata for a UK court judgment: parties, judges, neutral citation, court, dates. Use case_law_search to find the slug, then call this for orientation before reading specific paragraphs via judgment_get_paragraph.

Part of the Uk Legal server.

judgment_get_header is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE UK LEGAL →

Free to start. No card required.

AI agents call judgment_get_header to retrieve information from Uk Legal 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 judgment_get_header 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "judgment_get_header": {}
  }
}

See the full Uk Legal policy for all 29 tools.

Get this rule live on your own Uk Legal server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY UK LEGAL →

View all 29 tools →

These attack patterns abuse exactly the kind of access judgment_get_header gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so judgment_get_header only ever does what you allow.

SECURE UK LEGAL →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the judgment_get_header tool do? +

Get metadata for a UK court judgment: parties, judges, neutral citation, court, dates. Use case_law_search to find the slug, then call this for orientation before reading specific paragraphs via judgment_get_paragraph.. It is categorised as a Read tool in the Uk Legal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on judgment_get_header? +

Register the Uk Legal MCP server in PolicyLayer and add a rule for judgment_get_header: 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 Uk Legal. Nothing to install.

What risk level is judgment_get_header? +

judgment_get_header is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit judgment_get_header? +

Yes. Add a rate_limit block to the judgment_get_header 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.

How do I block judgment_get_header completely? +

Set action: deny in the PolicyLayer policy for judgment_get_header. 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.

What MCP server provides judgment_get_header? +

judgment_get_header is provided by the Uk Legal MCP server (bouch/uk-legal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Uk Legal tool call.

Deterministic rules across all 29 Uk Legal 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.