Low Risk

get_nfse_xml

Return the XML URL for an issued NFS-e.

How to control get_nfse_xml ↓

What get_nfse_xml does on Mcp Afip

AI agents call get_nfse_xml to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_nfse_xml needs a policy

This tool fetches and returns a URL pointer to an already-issued NFS-e (Nota Fiscal de Serviço Eletrônica, Brazilian electronic invoice equivalent) XML document. It performs no state changes, creates no data, executes no code, and deletes nothing. The operation is purely informational retrieval.

From the tool's definition Tool name 'get_nfse_xml' with description 'Return the XML URL for an issued NFS-e' indicates retrieval of a document URL without modification or deletion.

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

How to control get_nfse_xml

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_nfse_xml": {}
  }
}

get_nfse_xml is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Afip — 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_nfse_xml

What does the get_nfse_xml tool do? +

Return the XML URL for an issued NFS-e. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_nfse_xml? +

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

What risk level is get_nfse_xml? +

get_nfse_xml is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_nfse_xml? +

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

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

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

Enforce policy on every Mcp Afip tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.