// SCAN REPORT

Lfwin Payment

4 tools. 2 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

2 can modify or destroy data

2 read-only

4 tools total

Community server · catalogue entry verified 30/06/2026

How to control Lfwin Payment ↓

TOOL MAP

What Lfwin Payment exposes to your agents

Read (2) Write / Execute (0) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Lfwin Payment tools

Financial · Critical create_payment_order This tool creates payment orders, which commits financial obligations and moves money or engages payment processing. Financial · Critical refund_payment_order This tool directly moves money by processing refunds, which commits financial obligations and has irreversible consequences (funds returned to customer).

2 of Lfwin Payment's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Lfwin Payment

PolicyLayer is an MCP gateway — it sits between your AI agents and Lfwin Payment, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "create_payment_order": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Cap read operations

{
  "query_payment_order": {
    "limits": [
      {
        "counter": "query_payment_order_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Lfwin Payment — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON LFWIN PAYMENT →

Instant setup, no code required.

FULL CATALOGUE

All 4 Lfwin Payment tools

FINANCIAL 2 tools

Financial create_payment_order create_payment_order Financial refund_payment_order refund_payment_order

READ 2 tools

Read query_payment_order query_payment_order Read query_refund_status query_refund_status

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Lfwin Payment

Can an AI agent move money through the Lfwin Payment MCP server? +

Yes. The Lfwin Payment server exposes 2 financial tools including create_payment_order, refund_payment_order. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How many tools does the Lfwin Payment MCP server expose? +

4 tools across 2 categories: Financial, Read. 2 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Lfwin Payment? +

Register the Lfwin Payment MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Lfwin Payment tool call.

Deterministic rules across all 4 Lfwin Payment tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LFWIN PAYMENT →

Instant setup, no code required.

4 Lfwin Payment tools catalogued and risk-classified — across an index of 43,000+ MCP servers.