AI agents call retrieve_payment_gamertags to retrieve information from Zbd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical payment information that has already been processed. It queries existing data without creating charges, processing transactions, or moving funds. While it may access sensitive financial data, the act of retrieval itself is a Read operation.
From the tool's definition Tool name includes 'retrieve' and description states 'Retrieve all data about a Payment' - both indicate a query/lookup operation with no modification or financial transaction.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Retrieve all data about a Payment sent to ZBD User. It is categorised as a Read tool in the Zbd MCP Server, which means it retrieves data without modifying state.
Register the Zbd MCP server in PolicyLayer and add a rule for retrieve_payment_gamertags: 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.
retrieve_payment_gamertags is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the retrieve_payment_gamertags 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 retrieve_payment_gamertags. 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.
retrieve_payment_gamertags 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.
retrieve_payment_gamertags 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 →