Prepare any MYOB POST/PUT/PATCH/DELETE request. This does not call MYOB until approved and committed.
AI agents invoke myob_raw_prepare_mutation to trigger actions in MYOB Codex MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool prepares arbitrary POST/PUT/PATCH/DELETE mutations against the MYOB API, covering write, update, and destructive operations. While it stages the request (doesn't execute immediately), it encompasses the full spectrum up to and including DELETE operations.
From the tool's definition Prepare any MYOB POST/PUT/PATCH/DELETE request. This does not call MYOB until approved and committed.
Attacks that exploit this kind of access
Prepare any MYOB POST/PUT/PATCH/DELETE request. This does not call MYOB until approved and committed. It is categorised as a Execute tool in the MYOB Codex MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MYOB Codex MCP server in PolicyLayer and add a rule for myob_raw_prepare_mutation: 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_raw_prepare_mutation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the myob_raw_prepare_mutation 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_raw_prepare_mutation. 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_raw_prepare_mutation 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 →