Medium Risk

upsert_contact

Upsert (create or update) a contact identified by email (Marketing API)

How to control upsert_contact ↓

What upsert_contact does on Mcp Afip

AI agents use upsert_contact 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 upsert_contact needs a policy

Upsert operations (create or update) are reversible modifications to data—classified as Write. This is not Read (no side effects), not Execute (not arbitrary code/command execution), not Destructive (reversible), not Financial (no money movement).

From the tool's definition Tool name 'upsert_contact' and description explicitly states 'create or update' a contact, which are Write operations. The context is a Marketing API within an Argentine tax authority system.

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

How to control upsert_contact

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

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

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

What does the upsert_contact tool do? +

Upsert (create or update) a contact identified by email (Marketing API). 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 upsert_contact? +

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

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

Can I rate-limit upsert_contact? +

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

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

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