IDCloud: validate a Brazilian CPF with Receita Federal. Returns { valid, status (REGULAR | SUSPENSA | TITULAR FALECIDO | CANCELADA | NULA | PENDENTE), name, situation }. Optional birthdate enables a cross-check against the CPF registry.
AI agents call validate_cpf 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 is primarily a Read operation that queries an external database (Receita Federal) to retrieve CPF validation status and personal information. While it accesses sensitive PII (name, status, birthdate cross-check), it does not modify, delete, or execute arbitrary operations. It causes no financial transactions or destructive actions.
From the tool's definition Tool performs validation/lookup of Brazilian CPF data against Receita Federal registry. Returns status, name, and situation information. The description uses 'validate' and 'returns' indicating data retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access validate_cpf 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 validate_cpf:
{
"version": "1",
"default": "deny",
"tools": {
"validate_cpf": {}
}
} validate_cpf 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.
IDCloud: validate a Brazilian CPF with Receita Federal. Returns { valid, status (REGULAR | SUSPENSA | TITULAR FALECIDO | CANCELADA | NULA | PENDENTE), name, situation }. Optional birthdate enables a cross-check against the CPF registry. 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 validate_cpf: 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.
validate_cpf 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 validate_cpf 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 validate_cpf. 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.
validate_cpf 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.