Prepare update of a sales invoice. Requires approval before commit.
AI agents use myob_invoice_prepare_update to create or update resources in MYOB Codex MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MYOB Codex MCP environment.
The tool modifies (updates) a sales invoice, which is reversible data mutation. While it involves financial documents, it does not directly move money or create financial obligations—it prepares changes requiring explicit approval. This is Write rather than Financial.
From the tool's definition Tool name contains 'update' and description states 'Prepare update of a sales invoice. Requires approval before commit.' This indicates modification of existing financial documents.
Attacks that exploit this kind of access
Prepare update of a sales invoice. Requires approval before commit. It is categorised as a Write tool in the MYOB Codex MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MYOB Codex MCP server in PolicyLayer and add a rule for myob_invoice_prepare_update: 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 MYOB Codex MCP. Nothing to install.
myob_invoice_prepare_update 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 myob_invoice_prepare_update 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 myob_invoice_prepare_update. 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.
myob_invoice_prepare_update is provided by the MYOB Codex MCP server (jaeko44/myob-codex-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 →