create_payment

Create a payment in Sanka.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/create-payment.md

WHAT IT DOES

What create_payment does on Sanka MCP Server

AI agents use create_payment to commit financial operations through Sanka MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why create_payment is rated Critical

This tool creates payments, which constitutes a financial transaction that moves money or commits financial obligations. This is the most severe category and represents critical risk if an AI agent misuses it, as it could result in unauthorized money transfers.

From the tool's definition Tool name is 'create_payment' and description states 'Create a payment in Sanka.' The sibling tools on this server include financial operations like 'activate_invoice', 'activate_order', and 'approve_payroll_run', confirming this is a financial system.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_payment safely

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

create_payment Approval-gated

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

View as policy code

policy.json

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

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about create_payment

What does the create_payment tool do? +

Create a payment in Sanka. It is categorised as a Financial tool in the Sanka MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on create_payment? +

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

What risk level is create_payment? +

create_payment 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 create_payment? +

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

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

create_payment is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools → Critical-risk tools on this server →

Across the catalogue

create_payment on Shopmonkey MCP Server →request_x402_payment on Pop Pay →fundos_create_capital_call on Fundos →create_agent on Conviction → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →