Lists all user
AI agents call list_crypto_transactions 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 transaction history without modifying data. However, severity is elevated to 'medium' rather than 'low' because cryptocurrency transaction data is sensitive financial information that could enable wallet reconnaissance, transaction pattern analysis, or social engineering if exposed to an untrusted agent. No write, delete, or financial transaction capabilities are present.
From the tool's definition Tool name 'list_crypto_transactions' indicates retrieval operation ('list'). Description states 'Lists all user' (incomplete but clearly a listing/retrieval action).
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_crypto_transactions: 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_crypto_transactions 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_crypto_transactions 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_crypto_transactions. 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_crypto_transactions 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 →