AI agents use paystack_create_payment_page to commit financial operations through Paystack — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Creating a payment page is a financial operation that commits monetary obligations and facilitates fund transfers. Even though the individual tool description is empty, the server's explicit purpose ('accept payments') and the presence of payment-related sibling tools make it clear this tool moves or facilitates movement of money.
From the tool's definition Server description states the tool 'Enables AI assistants to accept payments...via Paystack API'. Tool name 'paystack_create_payment_page' combined with server's payment acceptance capability indicates financial transaction creation.
Attacks that exploit this kind of access
paystack_create_payment_page. 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.
Register the Paystack MCP server in PolicyLayer and add a rule for paystack_create_payment_page: 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.
paystack_create_payment_page is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the paystack_create_payment_page 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 paystack_create_payment_page. 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.
paystack_create_payment_page is provided by the Paystack MCP server (trinity-21/mcp-server-paystack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →