Medium Risk

update_cobv

Update an existing Pix due charge (cobv) by txid

How to control update_cobv ↓

What update_cobv does on Mcp Afip

AI agents use update_cobv to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.

Medium Risk

Why update_cobv needs a policy

This tool modifies existing payment charge records within a financial system, which constitutes a Write action. While it involves financial data, it does not move money or create financial obligations (Financial category); instead, it updates metadata or status of an existing charge.

From the tool's definition Tool name 'update_cobv' and description 'Update an existing Pix due charge (cobv) by txid' indicates modification of financial transaction data (Pix is a Brazilian instant payment system). The action is reversible through subsequent updates or corrections.

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

How to control update_cobv

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_cobv": {
      "limits": [
        {
          "counter": "update_cobv_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_cobv stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_cobv

What does the update_cobv tool do? +

Update an existing Pix due charge (cobv) by txid. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_cobv? +

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

update_cobv is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_cobv? +

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

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

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