Medium Risk

cache_cited_by

Fetch citing cases for a cached citation from jade.io and store them locally.

How to control cache_cited_by ↓

What cache_cited_by does on AusLaw MCP

AI agents use cache_cited_by to create or update resources in AusLaw MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AusLaw MCP environment.

Medium Risk

Why cache_cited_by needs a policy

The tool retrieves citing cases from jade.io (a read operation) but then stores/caches the results locally (a write operation). Since it persists data locally, Write is the most applicable category. The blast radius is low as it only stores legal citation metadata.

From the tool's definition fetch citing cases...and store them locally

Documented attack patterns abuse exactly the kind of access cache_cited_by gives an agent:

How to control cache_cited_by

PolicyLayer is an MCP gateway — it sits between your AI agents and AusLaw MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_cited_by:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cache_cited_by": {
      "limits": [
        {
          "counter": "cache_cited_by_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

cache_cited_by stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register AusLaw MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cache_cited_by

What does the cache_cited_by tool do? +

Fetch citing cases for a cached citation from jade.io and store them locally. It is categorised as a Write tool in the AusLaw MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cache_cited_by? +

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

What risk level is cache_cited_by? +

cache_cited_by is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cache_cited_by? +

Yes. Add a rate_limit block to the cache_cited_by 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 cache_cited_by completely? +

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

cache_cited_by is provided by the AusLaw MCP server (russellbrenner/auslaw-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AusLaw MCP tool call.

Start from AusLaw MCP, 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.

18 AusLaw MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.