AI agents call person to retrieve information from CourtListener MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The person tool likely retrieves information about judicial or legal individuals (judges, attorneys, parties) from the CourtListener database. This is consistent with the server's read-only search capabilities. No indication of data modification, deletion, code execution, or financial operations.
From the tool's definition Tool named 'person' on CourtListener MCP Server, which is described as enabling 'LLM-friendly access' to search 'legal opinions, court cases, judges, documents, and federal regulations.' Sibling tools (audio, batch_lookup_citations, cluster, court, docket,…
Documented attack patterns abuse exactly the kind of access person gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CourtListener MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for person:
{
"version": "1",
"default": "deny",
"tools": {
"person": {}
}
}person 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.
person. It is categorised as a Read tool in the CourtListener MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CourtListener MCP Server MCP server in PolicyLayer and add a rule for person: 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 CourtListener MCP Server. Nothing to install.
person 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 person 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 person. 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.
person is provided by the CourtListener MCP Server MCP server (travis-prall/court-listener-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CourtListener 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.
18 CourtListener MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.