KYC — validate a CPF, return name + DOB + restrictions + risk indicators. POST /v1/checks/person.
AI agents call person_check 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 is a Read operation—it queries and retrieves personal information (name, DOB, restrictions, risk indicators) without modifying any data. However, severity is medium rather than low because: (1) it accesses sensitive PII including date of birth; (2) it retrieves risk indicators that could enable discrimination; (3) misuse could support identity verification attacks or profiling.
From the tool's definition Tool performs KYC validation and returns personal data: 'validate a CPF, return name + DOB + restrictions + risk indicators'. The verb 'validate' and 'return' indicate data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access person_check 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 person_check:
{
"version": "1",
"default": "deny",
"tools": {
"person_check": {}
}
} person_check 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.
KYC — validate a CPF, return name + DOB + restrictions + risk indicators. POST /v1/checks/person. 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 person_check: 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.
person_check 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 person_check 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 person_check. 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.
person_check 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.