IDCheck: Brazilian judicial-records search. Covers federal and state courts (TRFs, TJs), labor courts (TRTs), and superior courts (STJ, STF). Returns case list with court, class, status, and filing date. Compliance-grade, not for scraping.
AI agents call court_records_search to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available Brazilian court records. It performs a read-only search operation that returns metadata about legal cases without creating, modifying, deleting, or executing any actions. The description emphasizes it is 'Compliance-grade, not for scraping,' reinforcing its read-only nature. No side effects beyond data retrieval occur.
From the tool's definition Tool name 'court_records_search' and description indicates it 'Returns case list with court, class, status, and filing date' — a retrieval operation with no modification or execution of external systems.
Documented attack patterns abuse exactly the kind of access court_records_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for court_records_search:
{
"version": "1",
"default": "deny",
"tools": {
"court_records_search": {}
}
}court_records_search 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.
IDCheck: Brazilian judicial-records search. Covers federal and state courts (TRFs, TJs), labor courts (TRTs), and superior courts (STJ, STF). Returns case list with court, class, status, and filing date. Compliance-grade, not for scraping. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for court_records_search: 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 Mcp Ap2. Nothing to install.
court_records_search 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 court_records_search 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 court_records_search. 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.
court_records_search is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.