Update invoice metadata such as tags.
AI agents use update_invoice to create or update resources in Morpheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Morpheus MCP Server environment.
This tool modifies invoice records by updating metadata and tags, which constitutes a Write operation. It is not Destructive because metadata updates are reversible. It is not Financial because it only modifies invoice metadata, not the financial transaction itself or payment amounts.
From the tool's definition Tool name 'update_invoice' and description 'Update invoice metadata such as tags' indicate modification of existing invoice data. The operation is reversible (metadata/tags can be changed again or reverted).
Attacks that exploit this kind of access
Update invoice metadata such as tags. It is categorised as a Write tool in the Morpheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for update_invoice: 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 Morpheus MCP Server. Nothing to install.
update_invoice 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_invoice 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_invoice. 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_invoice is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-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 →