Create and emit an NFCe (nota fiscal do consumidor eletronica)
AI agents use create_nfce to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Emitting an NFCe is a financial and legal obligation that records a completed consumer transaction. It commits a financial record to Brazil's tax authority (SEFAZ), is irreversible once authorized, and directly represents monetary transactions. This falls squarely in the Financial category with critical severity due to legal and financial binding nature.
From the tool's definition "Create and emit an NFCe (nota fiscal do consumidor eletronica)" — NFCe is a Brazilian electronic consumer invoice (fiscal document) that represents a legally binding financial transaction record emitted to tax authorities
Documented attack patterns abuse exactly the kind of access create_nfce gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for create_nfce:
{
"version": "1",
"default": "deny",
"tools": {
"create_nfce": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to create_nfce is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create and emit an NFCe (nota fiscal do consumidor eletronica). It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for create_nfce: 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 Ap2. Nothing to install.
create_nfce is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the create_nfce 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_nfce. 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_nfce is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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 Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.