wallet_history

View full transaction history — deposits, withdrawals, service charges, casino bets.

Server Purple Flea Casino purple-flea/agent-casino
Category Read
Risk class Low
Parameters 00 required

What wallet_history does on Purple Flea Casino

AI agents call wallet_history to retrieve information from Purple Flea Casino without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why wallet_history needs a policy

This tool queries historical financial transaction records without side effects. While it provides visibility into wallet activity (deposits, withdrawals, bets), viewing transaction history is a standard read operation with no capacity to move funds, alter balances, or execute trades. The blast radius of misuse is minimal—an AI agent could only enumerate or analyze past transactions, not commit financial harm.

From the tool's definition Tool name 'wallet_history' and description 'View full transaction history' indicate a read-only operation that retrieves and displays past transactions without creating, modifying, or deleting data.

Questions about wallet_history

What does the wallet_history tool do? +

View full transaction history — deposits, withdrawals, service charges, casino bets. It is categorised as a Read tool in the Purple Flea Casino MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wallet_history? +

Register the Purple Flea Casino MCP server in PolicyLayer and add a rule for wallet_history: 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 Purple Flea Casino. Nothing to install.

What risk level is wallet_history? +

wallet_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wallet_history? +

Yes. Add a rate_limit block to the wallet_history 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.

How do I block wallet_history completely? +

Set action: deny in the PolicyLayer policy for wallet_history. 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.

What MCP server provides wallet_history? +

wallet_history is provided by the Purple Flea Casino MCP server (purple-flea/agent-casino). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.