Low Risk

get_cae_status

Check CAE authorization status for an invoice

How to control get_cae_status ↓

What get_cae_status does on Mcp Afip

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

This tool performs a read-only lookup of CAE (Código de Autorización Electrónica) authorization status. CAE is a key component of Argentine electronic invoicing, but checking its status is purely informational with no side effects. The verb 'check' and the absence of any action words (create, modify, delete, execute) confirm this is a Read operation.

From the tool's definition Tool name 'get_cae_status' and description 'Check CAE authorization status for an invoice' indicate a query operation that retrieves status information without modifying or executing actions.

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

How to control get_cae_status

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

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

get_cae_status 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_cae_status

What does the get_cae_status tool do? +

Check CAE authorization status for an invoice. 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_cae_status? +

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

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

Can I rate-limit get_cae_status? +

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

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

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