Lists all user
AI agents call list_fiat_wallets to retrieve information from MCP Bitpanda Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves fiat wallet information without side effects. However, severity is elevated from 'low' to 'medium' because the data exposed includes financial account details (fiat wallets on a cryptocurrency exchange), which could enable fraud, account enumeration, or facilitate social engineering if accessed by an unauthorized agent.
From the tool's definition Tool name 'list_fiat_wallets' and description 'Lists all user' indicate a retrieval operation that queries wallet data without modification. The incomplete description suggests listing/fetching functionality typical of Read operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Lists all user. It is categorised as a Read tool in the MCP Bitpanda Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Bitpanda Server MCP server in PolicyLayer and add a rule for list_fiat_wallets: 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 MCP Bitpanda Server. Nothing to install.
list_fiat_wallets 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 list_fiat_wallets 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 list_fiat_wallets. 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.
list_fiat_wallets is provided by the MCP Bitpanda Server MCP server (matteoantoci/mcp-bitpanda). 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 →