AI agents use invoke_api_endpoint to commit financial operations through Zbd — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool can invoke arbitrary endpoints of the ZBD Payments API, which handles financial operations including charges, withdrawals, vouchers, and Lightning Network payments. Given the sibling tools and the payments context, misuse could trigger unauthorized financial transactions, making this Financial/critical.
From the tool's definition 'Invoke an endpoint in the Zbd Payments TypeScript API' — this is a payments API invocation tool on a server with sibling tools like create_charge_gamertags, create_lightning_charges, create_vouchers, create_withdrawal_requests
Attacks that exploit this kind of access
Invoke an endpoint in the Zbd Payments TypeScript API. Note: use the. It is categorised as a Financial tool in the Zbd MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Zbd MCP server in PolicyLayer and add a rule for invoke_api_endpoint: 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 Zbd. Nothing to install.
invoke_api_endpoint 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 invoke_api_endpoint 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 invoke_api_endpoint. 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.
invoke_api_endpoint is provided by the Zbd MCP server (zebedeeio/zbd-payments-typescript-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
invoke_api_endpoint is one line of Zbd's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →