Address normalization + validation against CORREIOS + IBGE — canonical address, CEP, neighborhood, city, state, geocode. POST /v1/datasets/addresses.
AI agents call address_validation 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 retrieves and validates address information against reference databases, returning standardized data. Despite the POST method, the operation is read-only — it queries external sources (Brazilian postal and geographic databases) to normalize and validate input without creating, modifying, or deleting data. No side effects, no financial impact, no irreversible actions.
From the tool's definition Tool performs address 'normalization + validation' against external databases (CORREIOS + IBGE), returning canonical address, CEP, neighborhood, city, state, geocode.
Documented attack patterns abuse exactly the kind of access address_validation 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 address_validation:
{
"version": "1",
"default": "deny",
"tools": {
"address_validation": {}
}
} address_validation 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.
Address normalization + validation against CORREIOS + IBGE — canonical address, CEP, neighborhood, city, state, geocode. POST /v1/datasets/addresses. 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 address_validation: 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.
address_validation 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 address_validation 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 address_validation. 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.
address_validation 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.