AI agents call retrieve_user_data_oauth2 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 is a Read operation as it retrieves user information. However, the severity is medium rather than low because: (1) user data can include sensitive personal/financial information given the financial context of the ZBD server (evidenced by sibling tools like create_charge_lightning_address, create_withdrawal_requests), and (2) an AI agent with unauthorized access to this tool could extract private user details.
From the tool's definition Tool name includes 'retrieve_user_data' and description states 'Fetch user-related information about a logged-in ZBD User.' The verbs 'retrieve' and 'fetch' indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
Fetch user-related information about a logged-in 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_user_data_oauth2: 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_user_data_oauth2 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_user_data_oauth2 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_user_data_oauth2. 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_user_data_oauth2 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_user_data_oauth2 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 →