Low Risk

retrieveDocument

Retrieves a list of electronic fiscal documents (NF-e, CT-e, MDF-e, Minuta CT-e) from the AverbePorto API based on specified filter criteria. Filters include document type, date range, date type (emission, update, send), document number (9 char max), involved parties (CNPJs), status, and more. Su...

High parameter count (22 properties)

Part of the AverbePorto MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call retrieveDocument to retrieve information from AverbePorto without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though retrieveDocument only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

ghsix-averbeporto-mcp.yaml
tools:
  retrieveDocument:
    rules:
      - action: allow

See the full AverbePorto policy for all 5 tools.

Tool Name retrieveDocument
Category Read
Risk Level Low

Agents calling read-class tools like retrieveDocument have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the retrieveDocument tool do? +

Retrieves a list of electronic fiscal documents (NF-e, CT-e, MDF-e, Minuta CT-e) from the AverbePorto API based on specified filter criteria. Filters include document type, date range, date type (emission, update, send), document number (9 char max), involved parties (CNPJs), status, and more. Supports pagination. Requires an active `sessionId`.. It is categorised as a Read tool in the AverbePorto MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retrieveDocument? +

Add a rule in your Intercept YAML policy under the tools section for retrieveDocument. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AverbePorto MCP server.

What risk level is retrieveDocument? +

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

Can I rate-limit retrieveDocument? +

Yes. Add a rate_limit block to the retrieveDocument rule in your Intercept 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 retrieveDocument completely? +

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

retrieveDocument is provided by the AverbePorto MCP server (GHSix/averbeporto-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.