Manually exchange an OAuth code for MYOB tokens and save businessId context.
AI agents use myob_oauth_exchange_code 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.
This tool performs an OAuth token exchange and persists the resulting tokens along with a businessId. It creates/saves new authentication state, which is a Write operation. The severity is high because misuse could allow an attacker to hijack an authenticated MYOB session by exchanging a stolen OAuth code, gaining full access to financial accounting data and all mutating operations on the server.
From the tool's definition 'exchange an OAuth code for MYOB tokens and save businessId context' — stores/saves credential tokens and business context
Attacks that exploit this kind of access
Manually exchange an OAuth code for MYOB tokens and save businessId context. 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_oauth_exchange_code: 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_oauth_exchange_code 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_oauth_exchange_code 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_oauth_exchange_code. 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_oauth_exchange_code 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 →