List subscription plans. Endpoint: GET /plans
AI agents call list_plans 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 straightforward read operation that retrieves subscription plan information from the AFIP tax authority system. GET requests are inherently safe queries that do not modify data. The blast radius of misuse is minimal—an agent could only enumerate available plans, which is typically non-sensitive catalog data. No financial transactions, data creation, deletion, or external operations are performed.
From the tool's definition Tool name is 'list_plans' and description explicitly states 'List subscription plans' with GET endpoint, indicating pure data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access list_plans 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_plans:
{
"version": "1",
"default": "deny",
"tools": {
"list_plans": {}
}
} list_plans 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 subscription plans. Endpoint: GET /plans. 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_plans: 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_plans 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_plans 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_plans. 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_plans 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.