Prepare recording a customer payment. High-risk approval required.
AI agents use myob_customer_payment_prepare_record to commit financial operations through MYOB Codex MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Recording a customer payment directly involves financial transactions — committing received funds against invoices. Even in a 'prepare' (staged/approval) pattern, this tool initiates a financial obligation and is explicitly flagged as 'High-risk'.
From the tool's definition 'Prepare recording a customer payment. High-risk approval required.'
Attacks that exploit this kind of access
Prepare recording a customer payment. High-risk approval required. It is categorised as a Financial tool in the MYOB Codex MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MYOB Codex MCP server in PolicyLayer and add a rule for myob_customer_payment_prepare_record: 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_customer_payment_prepare_record is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the myob_customer_payment_prepare_record 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_customer_payment_prepare_record. 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_customer_payment_prepare_record 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 →