Mark an inquiry as approved. This records your final decision on the Persona inquiry — useful for dashboard reporting and Persona
AI agents use approve_inquiry to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.
The tool writes/updates inquiry status in what appears to be a tax authority system. While reversible (not destructive), it changes recorded decisions that could affect tax compliance workflows or dashboard reporting. The medium severity reflects that misuse could alter inquiry records and reporting, but without direct financial movement or data destruction.
From the tool's definition 'Mark an inquiry as approved. This records your final decision on the Persona inquiry' — the tool modifies the status of an inquiry record, making a reversible change to data state.
Documented attack patterns abuse exactly the kind of access approve_inquiry 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 approve_inquiry:
{
"version": "1",
"default": "deny",
"tools": {
"approve_inquiry": {
"limits": [
{
"counter": "approve_inquiry_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} approve_inquiry stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Mark an inquiry as approved. This records your final decision on the Persona inquiry — useful for dashboard reporting and Persona. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for approve_inquiry: 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.
approve_inquiry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the approve_inquiry 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 approve_inquiry. 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.
approve_inquiry 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.