Critical Risk →

create_nfe

Create and emit an NFe (nota fiscal eletronica)

How to control create_nfe ↓

What create_nfe does on Mcp Ap2

AI agents use create_nfe to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why create_nfe needs a policy

Creating and emitting a Nota Fiscal Eletrônica (NFe) is a legally binding financial document in Brazil that records commercial transactions, triggers tax obligations, and constitutes an official fiscal record. Misuse could result in fraudulent invoicing, tax evasion, or unauthorized financial commitments, making this a Financial/critical risk tool.

From the tool's definition Create and emit an NFe (nota fiscal eletronica) — NFe is an official Brazilian electronic invoice with legal and financial implications

Documented attack patterns abuse exactly the kind of access create_nfe gives an agent:

How to control create_nfe

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_nfe:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_nfe": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to create_nfe is blocked until a human approves it. The rest of the server keeps working.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_nfe

What does the create_nfe tool do? +

Create and emit an NFe (nota fiscal 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.

How do I enforce a policy on create_nfe? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for create_nfe: 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.

What risk level is create_nfe? +

create_nfe is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit create_nfe? +

Yes. Add a rate_limit block to the create_nfe 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.

How do I block create_nfe completely? +

Set action: deny in the PolicyLayer policy for create_nfe. 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.

What MCP server provides create_nfe? +

create_nfe 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.

Enforce policy on every Mcp Ap2 tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.