Low Risk

list_connectors

Lists supported Brazilian banks (connectors). Pluggy endpoint: GET /connectors. Optional filters: name, types (e.g. PERSONAL_BANK, BUSINESS_BANK), countries (BR), sandbox.

How to control list_connectors ↓

What list_connectors does on Mcp Afip

AI agents call list_connectors 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 list_connectors needs a policy

This tool only queries and retrieves informational data about supported banking integrations. It has no side effects, does not modify any data, and does not execute operations or trigger external services. The optional filters (name, types, countries, sandbox) are simple query parameters for filtering a list, which is typical of Read operations.

From the tool's definition Tool description explicitly states "Lists supported Brazilian banks (connectors)" and references "GET /connectors" — a read-only HTTP method that retrieves static configuration data about available bank connectors.

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

How to control list_connectors

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

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

list_connectors 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 list_connectors

What does the list_connectors tool do? +

Lists supported Brazilian banks (connectors). Pluggy endpoint: GET /connectors. Optional filters: name, types (e.g. PERSONAL_BANK, BUSINESS_BANK), countries (BR), sandbox. 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 list_connectors? +

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

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

Can I rate-limit list_connectors? +

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

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

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