getUserPayment

Get your payment methods configured in P2P. The returned

SERVERBybit MCP Server SOURCEbybit-exchange/trading-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bybit-exchange-trading-mcp/getuserpayment.md

WHAT IT DOES

What getUserPayment does on Bybit MCP Server

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

RISK

Why getUserPayment is rated Low

This tool retrieves payment method information from a user's P2P account settings. It performs no creation, modification, deletion, code execution, or financial transactions. The operation is purely informational and read-only. Even though it touches payment-related data, it does not move funds or create financial obligations - it only fetches existing configuration data.

From the tool's definition Tool name is 'getUserPayment' and description states 'Get your payment methods configured in P2P' - the verb 'Get' and context of retrieving configured payment methods indicate a read-only operation that retrieves existing data without modification or side…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getUserPayment safely

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

getUserPayment Allowed

getUserPayment 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": {
    "getUserPayment": {}
  }
}

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

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

FAQ

Questions about getUserPayment

What does the getUserPayment tool do? +

Get your payment methods configured in P2P. The returned. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getUserPayment? +

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

What risk level is getUserPayment? +

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

Can I rate-limit getUserPayment? +

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

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

getUserPayment is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 380 Bybit MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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