Create a new Money Lover wallet.
AI agents use add_wallet to create or update resources in Money Lover MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Money Lover MCP Server environment.
This tool creates a new wallet in the financial system, modifying the user's data structure. While it creates data (Write category), it does not involve actual money movement (not Financial) and is reversible (not Destructive). The severity is medium because an AI agent could create unauthorized wallets, potentially confusing the user's financial tracking, but the action can be undone by deleting the wallet.
From the tool's definition Tool name is 'add_wallet' and description states 'Create a new Money Lover wallet' — the verb 'Create' indicates data creation, a reversible write operation.
Attacks that exploit this kind of access
Create a new Money Lover wallet. It is categorised as a Write tool in the Money Lover MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Money Lover MCP Server MCP server in PolicyLayer and add a rule for add_wallet: 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 Money Lover MCP Server. Nothing to install.
add_wallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_wallet 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 add_wallet. 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.
add_wallet is provided by the Money Lover MCP Server MCP server (juansebashr/moneylover-mcp). 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 →