Low Risk

get_instances

List all WhatsApp instances

How to control get_instances ↓

What get_instances does on Mcp Afip

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

This tool performs data retrieval without side effects. It lists existing instances without creating, modifying, deleting, or executing any operations. While the server context is AFIP (Argentine tax authority), this specific tool is a simple informational query about WhatsApp instances, posing minimal risk if misused by an AI agent.

From the tool's definition Tool name 'get_instances' combined with description 'List all WhatsApp instances' indicates a read-only operation that retrieves data about WhatsApp instances without modifying or executing actions.

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

How to control get_instances

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

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

get_instances 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_instances

What does the get_instances tool do? +

List all WhatsApp instances. 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_instances? +

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

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

Can I rate-limit get_instances? +

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

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

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