card_brand_detect

Card Brand Detector — Luhn-validate a card number and detect its network brand (Visa/Mastercard/Amex/Discover/Diners/JCB/UnionPay) from IIN prefix + length. Formula only, not a real-card check.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/card-brand-detect.md

WHAT IT DOES

What card_brand_detect does on Gateway

AI agents call card_brand_detect to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`number`	string	Yes	Card number (spaces/dashes ignored)

Parameters from the server's own tool schema.

RISK

Why card_brand_detect is rated Low

This tool only analyzes card number patterns using the Luhn algorithm and IIN (Issuer Identification Number) prefix matching to classify card types. It does not process payments, access real card data, execute transactions, or modify any state. The explicit disclaimer 'not a real-card check' confirms it is a pure formula-based classifier.

From the tool's definition Tool description states 'Luhn-validate a card number and detect its network brand' and explicitly clarifies 'Formula only, not a real-card check.' The tool performs validation and detection based on card number format (IIN prefix and length), which is a…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs card_brand_detect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For card_brand_detect, this is the rule to start with:

card_brand_detect Allowed

card_brand_detect is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "card_brand_detect": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every card_brand_detect call is checked against it from then on.

FAQ

Questions about card_brand_detect

What does the card_brand_detect tool do? +

Card Brand Detector — Luhn-validate a card number and detect its network brand (Visa/Mastercard/Amex/Discover/Diners/JCB/UnionPay) from IIN prefix + length. Formula only, not a real-card check. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.

What parameters does card_brand_detect accept? +

card_brand_detect accepts 1 parameter: number. Required: number. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on card_brand_detect? +

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

What risk level is card_brand_detect? +

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

Can I rate-limit card_brand_detect? +

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

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

card_brand_detect is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →