List available cities for shipping
AI agents call list_cities 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 static reference data (city lists for shipping options). It performs no modification, execution, or deletion of data. The read-only nature and lack of state-changing operations place it in the Read category with low severity, as misuse poses minimal risk to the system or data integrity.
From the tool's definition Tool name is 'list_cities' and description states 'List available cities for shipping' — a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_cities 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 list_cities:
{
"version": "1",
"default": "deny",
"tools": {
"list_cities": {}
}
} list_cities 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.
List available cities for shipping. 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 list_cities: 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.
list_cities 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 list_cities 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 list_cities. 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.
list_cities 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.