Critical Risk →

issue_card

Issue a card (debit / credit / prepaid / virtual) against a Dock account. Card issuing is Dock

How to control issue_card ↓

What issue_card does on Mcp Afip

AI agents use issue_card to commit financial operations through Mcp Afip — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why issue_card needs a policy

Issuing a payment card creates a financial instrument tied to an account, committing financial obligations and enabling future financial transactions. This falls squarely in the Financial category with critical severity due to the potential for fraud, unauthorized spending, and account compromise if misused.

From the tool's definition Issue a card (debit / credit / prepaid / virtual) against a Dock account

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

How to control issue_card

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "issue_card": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to issue_card is blocked until a human approves it. The rest of the server keeps working.

  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.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about issue_card

What does the issue_card tool do? +

Issue a card (debit / credit / prepaid / virtual) against a Dock account. Card issuing is Dock. It is categorised as a Financial tool in the Mcp Afip MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on issue_card? +

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

issue_card is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit issue_card? +

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

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

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