Valida e confirma titularidade de uma lista de CPFs em paralelo consultando o TRT3.
AI agents call check_multiple_cpfs to retrieve information from Cpf Validador without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This specific tool performs read-only validation and lookup of CPF ownership status. The primary action is querying a database to confirm titularidade (ownership/identity verification). This is fundamentally a Read operation.
From the tool's definition Tool description states 'Valida e confirma titularidade de uma lista de CPFs' (validates and confirms ownership of a list of CPFs) — this is a query/lookup operation against TRT3 (labor court database).
Documented attack patterns abuse exactly the kind of access check_multiple_cpfs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cpf Validador, and nothing reaches the server without passing your rules. This is the rule we recommend for check_multiple_cpfs:
{
"version": "1",
"default": "deny",
"tools": {
"check_multiple_cpfs": {}
}
}check_multiple_cpfs 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.
Valida e confirma titularidade de uma lista de CPFs em paralelo consultando o TRT3. It is categorised as a Read tool in the Cpf Validador MCP Server, which means it retrieves data without modifying state.
Register the Cpf Validador MCP server in PolicyLayer and add a rule for check_multiple_cpfs: 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 Cpf Validador. Nothing to install.
check_multiple_cpfs 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 check_multiple_cpfs 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 check_multiple_cpfs. 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.
check_multiple_cpfs is provided by the Cpf Validador MCP server (opastorello/cpf-validador). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cpf Validador, 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.
6 Cpf Validador tools catalogued and risk-classified — across an index of 43,000+ MCP servers.