Generates a new OTP and sends to customer for transfer verification
AI agents invoke resend_transfers_otp to trigger actions in Paystack. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — generating and delivering an OTP message to a customer — as part of a transfer verification flow. While it doesn't directly move money, it is a critical step in authorizing financial transfers. Misuse could flood customers with OTP messages or be used to manipulate transfer authorization flows.
From the tool's definition Generates a new OTP and sends to customer for transfer verification
Documented attack patterns abuse exactly the kind of access resend_transfers_otp gives an agent:
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 resend_transfers_otp:
{
"version": "1",
"default": "deny",
"tools": {
"resend_transfers_otp": {
"limits": [
{
"counter": "resend_transfers_otp_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} resend_transfers_otp stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generates a new OTP and sends to customer for transfer verification. It is categorised as a Execute tool in the Paystack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Paystack MCP server in PolicyLayer and add a rule for resend_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.
resend_transfers_otp is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the resend_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.
Set action: deny in the PolicyLayer policy for resend_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.
resend_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.
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.