List inquiries, filterable by reference-id (your internal user id) or status. Useful for reconciling state or finding a user
AI agents call list_inquiries 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 filters inquiries without creating, modifying, deleting, or executing any actions. It is a standard data query operation with no side effects, fitting the 'Read' category. The low severity reflects that listing inquiries poses minimal risk even if misused by an agent, as it only exposes existing inquiry data rather than enabling destructive or financial operations.
From the tool's definition Tool description states 'List inquiries, filterable by reference-id or status.' The verb 'list' and the filtering capability indicate data retrieval with no modification. The use case of 'reconciling state or finding a user' confirms read-only operations.
Documented attack patterns abuse exactly the kind of access list_inquiries 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_inquiries:
{
"version": "1",
"default": "deny",
"tools": {
"list_inquiries": {}
}
} list_inquiries 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 inquiries, filterable by reference-id (your internal user id) or status. Useful for reconciling state or finding a user. 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_inquiries: 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_inquiries 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_inquiries 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_inquiries. 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_inquiries 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.