Critical Risk →

enable_transfers_otp

Enable OTP requirement for transfers

How to control enable_transfers_otp ↓

What enable_transfers_otp does on Paystack

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

Critical Risk

Why enable_transfers_otp needs a policy

This tool modifies security controls governing financial transfers. Enabling OTP for transfers is a financial security configuration that directly affects the ability to move money. Misuse could be used as part of an attack chain to manipulate transfer authorization flows, and it is paired with a sibling tool 'disable_transfers_otp' suggesting these controls gate financial transactions.

From the tool's definition Enable OTP requirement for transfers

Documented attack patterns abuse exactly the kind of access enable_transfers_otp gives an agent:

How to control enable_transfers_otp

PolicyLayer is an MCP gateway — it sits between your AI agents and Paystack, and nothing reaches the server without passing your rules. This is the rule we recommend for enable_transfers_otp:

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

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

  1. Create a free account and register Paystack — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about enable_transfers_otp

What does the enable_transfers_otp tool do? +

Enable OTP requirement for transfers. It is categorised as a Financial tool in the Paystack MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on enable_transfers_otp? +

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

What risk level is enable_transfers_otp? +

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

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

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

enable_transfers_otp is provided by the Paystack MCP server (kohasummons/paystack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Paystack tool call.

Start from Paystack, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

28 Paystack tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.