pagarme_update_customer_metadata

WHAT IT DOES

What pagarme_update_customer_metadata does on Payments MCP

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

WHY IT NEEDS A POLICY

Why pagarme_update_customer_metadata needs a policy

This tool modifies customer metadata in a financial payment system (Pagar.me), which is a Write operation—data is created or altered reversibly. It is not Destructive (metadata is updated, not deleted), not Financial per se (it doesn't move money, only updates customer records), and not Execute (it doesn't run arbitrary code).

From the tool's definition Tool name 'pagarme_update_customer_metadata' with description 'Atualiza o metadata de um customer no Pagar.me' (Updates customer metadata on Pagar.me). The 'update' action modifies customer data reversibly within the payment gateway.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pagarme_update_customer_metadata Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pagarme_update_customer_metadata": {
      "limits": [
        {
          "counter": "pagarme_update_customer_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Payments MCP, so you can run agents against it safely.

FAQ

Questions about pagarme_update_customer_metadata

What does the pagarme_update_customer_metadata tool do? +

Atualiza o metadata de um customer no Pagar.me. It is categorised as a Write tool in the Payments MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pagarme_update_customer_metadata? +

Register the Payments MCP server in PolicyLayer and add a rule for pagarme_update_customer_metadata: 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 Payments MCP. Nothing to install.

What risk level is pagarme_update_customer_metadata? +

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

Can I rate-limit pagarme_update_customer_metadata? +

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

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

pagarme_update_customer_metadata is provided by the Payments MCP server (lpillonwp/mcp-payments). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.