AI agents call get_court_filings to retrieve information from LegalMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool follows the naming pattern and purpose of other data retrieval tools on the server. No description is provided, which lowers confidence slightly, but the 'get_' prefix and sibling context strongly indicate this is a read-only operation that queries and returns court filing information without creating, modifying, or deleting data.
From the tool's definition Tool name 'get_court_filings' indicates retrieval of existing court filing data. Sibling tools like 'get_case_details', 'get_case_record', 'get_federal_case', and 'get_matter_documents' are all read operations that retrieve data without modification.
Documented attack patterns abuse exactly the kind of access get_court_filings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LegalMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_court_filings:
{
"version": "1",
"default": "deny",
"tools": {
"get_court_filings": {}
}
}get_court_filings 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.
get_court_filings. It is categorised as a Read tool in the LegalMCP MCP Server, which means it retrieves data without modifying state.
Register the Legal MCP server in PolicyLayer and add a rule for get_court_filings: 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 LegalMCP. Nothing to install.
get_court_filings 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 get_court_filings 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 get_court_filings. 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.
get_court_filings is provided by the Legal MCP server (mahender22/legal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LegalMCP, 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 LegalMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.