Store or update a citation in the local project cache. Assigns a biblatex-compatible cite key on first use. Returns the cite key and canonical AGLC4 string.
AI agents use cache_citation 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.
The tool writes to a local cache by storing or updating citations. This is reversible (cache can be cleared or entries modified), has no destructive capability, involves no execution of arbitrary code, and creates no financial obligations. It is a straightforward data persistence operation. Severity is low because misuse would only affect the user's local citation cache with minimal blast radius.
From the tool's definition Tool description explicitly states 'Store or update a citation in the local project cache' — this is a write operation that creates or modifies data (citation cache entries) reversibly.
Documented attack patterns abuse exactly the kind of access cache_citation gives an agent:
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_citation:
{
"version": "1",
"default": "deny",
"tools": {
"cache_citation": {
"limits": [
{
"counter": "cache_citation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cache_citation 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.
Free to start. No card required.
Store or update a citation in the local project cache. Assigns a biblatex-compatible cite key on first use. Returns the cite key and canonical AGLC4 string. 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.
Register the AusLaw MCP server in PolicyLayer and add a rule for cache_citation: 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.
cache_citation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cache_citation 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 cache_citation. 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.
cache_citation 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.
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.