manual_repay

Manual repay (with auto conversion if needed).

SERVERBybit SOURCEjohnnywic/bybit-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/johnnywic-bybit-mcp/manual-repay.md

WHAT IT DOES

What manual_repay does on Bybit

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

RISK

Why manual_repay is rated Critical

This tool performs a financial repayment operation on the Bybit exchange, which involves moving funds to repay debt (likely margin or loan). It commits a financial obligation and can trigger automatic asset conversion, making it a Financial category action with high severity due to potential unintended fund movements or forced liquidation of assets.

From the tool's definition Manual repay (with auto conversion if needed)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manual_repay safely

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

manual_repay Approval-gated

Any call to manual_repay 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": {
    "manual_repay": {
      "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 Bybit, apply this rule, and every manual_repay call is checked against it from then on.

FAQ

Questions about manual_repay

What does the manual_repay tool do? +

Manual repay (with auto conversion if needed). It is categorised as a Financial tool in the Bybit MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on manual_repay? +

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

What risk level is manual_repay? +

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

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

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

manual_repay is provided by the Bybit MCP server (johnnywic/bybit-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, and thousands of servers like it.

This server

All 245 Bybit tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

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