Low Risk

list_stored_payment_methods

List a shopper

How to control list_stored_payment_methods ↓

What list_stored_payment_methods does on Mcp Afip

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

This tool retrieves or lists existing payment method data associated with a shopper. It performs a read-only query with no modifications, deletions, or financial transactions. While payment data is sensitive, the tool itself only accesses/displays it without altering state or committing obligations.

From the tool's definition Tool name 'list_stored_payment_methods' and verb 'List' in description indicate data retrieval. The description states 'List a shopper', which is a query operation with no side effects.

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

How to control list_stored_payment_methods

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

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

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

What does the list_stored_payment_methods tool do? +

List a shopper. 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 list_stored_payment_methods? +

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

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

Can I rate-limit list_stored_payment_methods? +

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

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

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