Composite fraud risk score (0-1000) for a transaction context (CPF + email + phone + IP + device). Returns score, risk factors, decision recommendation. POST /v1/datasets/antifraud.
AI agents call antifraud_score 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.
Although the HTTP verb is POST, the tool's function is purely analytical and informational—it retrieves or computes a fraud score based on input parameters (CPF, email, phone, IP, device). It has no side effects on data, does not execute code or external operations, and does not commit financial obligations.
From the tool's definition Tool returns a fraud risk score and analysis data (score, risk factors, decision recommendation) without modifying any records or triggering financial transactions.
Documented attack patterns abuse exactly the kind of access antifraud_score 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 antifraud_score:
{
"version": "1",
"default": "deny",
"tools": {
"antifraud_score": {}
}
}antifraud_score 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.
Composite fraud risk score (0-1000) for a transaction context (CPF + email + phone + IP + device). Returns score, risk factors, decision recommendation. POST /v1/datasets/antifraud. 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 antifraud_score: 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.
antifraud_score 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 antifraud_score 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 antifraud_score. 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.
antifraud_score 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.