AI agents call search_federal_cases to retrieve information from Legal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches federal cases—a retrieval operation with no side effects. Searching legal databases does not modify, execute code, delete, or transfer funds. The empty description lowers confidence slightly, but the naming convention and sibling tool patterns strongly indicate a read-only search operation typical of legal research platforms.
From the tool's definition Tool name is 'search_federal_cases' and server context indicates US case law search functionality. Description is empty, but sibling tools (find_cited_cases, find_citing_cases, get_case_details, get_case_record, get_federal_case) and server purpose confirm…
Attacks that exploit this kind of access
search_federal_cases. It is categorised as a Read tool in the Legal MCP Server, which means it retrieves data without modifying state.
Register the Legal MCP server in PolicyLayer and add a rule for search_federal_cases: 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 Legal. Nothing to install.
search_federal_cases 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 search_federal_cases 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 search_federal_cases. 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.
search_federal_cases is provided by the Legal MCP server (jscottym/legal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →