Request an SP-API report. Report is generated asynchronously — poll with get_report until processingStatus is DONE, then fetch the reportDocumentId.
AI agents use create_report 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 creates a report request (a new resource) on the SP-API, which is a reversible write operation. It does not delete data, execute arbitrary code, or move money. The async polling pattern confirms it initiates a job rather than just reading existing data.
From the tool's definition 'Request an SP-API report. Report is generated asynchronously' — creates a report generation request, a write action that initiates a new resource/job on the server.
Documented attack patterns abuse exactly the kind of access create_report 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 create_report:
{
"version": "1",
"default": "deny",
"tools": {
"create_report": {
"limits": [
{
"counter": "create_report_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_report 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.
Request an SP-API report. Report is generated asynchronously — poll with get_report until processingStatus is DONE, then fetch the reportDocumentId. 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 create_report: 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.
create_report 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 create_report 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 create_report. 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.
create_report 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.