Medium Risk

close_mdfe

Close/finalize an MDFe (encerramento) after trip completion

How to control close_mdfe ↓

What close_mdfe does on Mcp Ap2

AI agents use close_mdfe to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.

Medium Risk

Why close_mdfe needs a policy

Closing/finalizing an MDFe (Manifesto Eletrônico de Documentos Fiscais) is a write/update operation that changes the document's state to finalized. While it is not easily reversible, it is a standard business process completion action rather than a deletion. The fiscal document remains in the system; its status is updated.

From the tool's definition Close/finalize an MDFe (encerramento) after trip completion

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

How to control close_mdfe

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "close_mdfe": {
      "limits": [
        {
          "counter": "close_mdfe_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about close_mdfe

What does the close_mdfe tool do? +

Close/finalize an MDFe (encerramento) after trip completion. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on close_mdfe? +

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

close_mdfe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit close_mdfe? +

Yes. Add a rate_limit block to the close_mdfe 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 close_mdfe completely? +

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

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