Create and emit an NFSe (nota fiscal de servico)
AI agents use create_nfse 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.
This tool creates and issues NFSe (electronic service invoices), which are legally binding tax documents in Argentina's fiscal system. Creation of tax invoices is a Write operation (creates formal records reversibly), but the context of tax authority (AFIP) systems and financial document generation elevates severity to high due to potential for fraud, double-billing, or creation of false tax records that could have…
From the tool's definition Tool name 'create_nfse' and description 'Create and emit an NFSe (nota fiscal de servico)' indicate creation of formal tax documents (service invoices).
Documented attack patterns abuse exactly the kind of access create_nfse 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_nfse:
{
"version": "1",
"default": "deny",
"tools": {
"create_nfse": {
"limits": [
{
"counter": "create_nfse_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_nfse 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.
Create and emit an NFSe (nota fiscal de servico). 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_nfse: 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_nfse 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_nfse 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_nfse. 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_nfse 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.