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 Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries judicial records and retrieves publicly available court information without modifying, deleting, or executing external operations. The search operation and result set (case metadata) constitute a Read operation with minimal blast radius.
From the tool's definition Tool returns case list with court, class, status, and filing date. Keywords: 'search' and 'Returns case list' indicate data retrieval. Explicit limitation 'not for scraping' reinforces read-only intended use.
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 Afip, 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 Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip 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 Afip. 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 Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, 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 Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.