Update a manual crypto asset
AI agents use update_manual_crypto to create or update resources in Lunch Money MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lunch Money MCP Server environment.
This tool updates/modifies an existing manual crypto asset in the Lunch Money account. It's a Write operation as it changes financial asset data reversibly. Severity is high because cryptocurrency assets represent real financial holdings and incorrect updates could misrepresent a user's financial position, though it does not directly move money.
From the tool's definition 'Update a manual crypto asset' — modifies existing cryptocurrency asset data
Attacks that exploit this kind of access
Update a manual crypto asset. It is categorised as a Write tool in the Lunch Money MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lunch Money MCP Server MCP server in PolicyLayer and add a rule for update_manual_crypto: 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 Lunch Money MCP Server. Nothing to install.
update_manual_crypto 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 update_manual_crypto 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 update_manual_crypto. 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.
update_manual_crypto is provided by the Lunch Money MCP Server MCP server (matiasl13/lunchmoney-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 →