myob_approval_deny · MYOB Codex MCP: Risk & Policy

WHAT IT DOES

What myob_approval_deny does on MYOB Codex MCP

AI agents use myob_approval_deny 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.

WHY IT NEEDS A POLICY

Why myob_approval_deny needs a policy

This tool modifies approval workflow state by denying previously prepared or approved write operations. While it does not directly mutate business data (accounts, bills, etc.), it changes the administrative state of pending mutations. It is reversible (a denied operation could be re-approved or resubmitted), making it Write rather than Destructive.

From the tool's definition Tool name is 'myob_approval_deny' and description states it will 'Deny a prepared or approved MYOB write operation.' This directly modifies the state of approval records by changing their status from pending/approved to denied.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

myob_approval_deny Rate-limited

myob_approval_deny stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "myob_approval_deny": {
      "limits": [
        {
          "counter": "myob_approval_deny_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MYOB Codex MCP, so you can run agents against it safely.

FAQ

Questions about myob_approval_deny

What does the myob_approval_deny tool do? +

Deny a prepared or approved MYOB write operation. 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.

How do I enforce a policy on myob_approval_deny? +

Register the MYOB Codex MCP server in PolicyLayer and add a rule for myob_approval_deny: 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.

What risk level is myob_approval_deny? +

myob_approval_deny is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit myob_approval_deny? +

Yes. Add a rate_limit block to the myob_approval_deny 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.

How do I block myob_approval_deny completely? +

Set action: deny in the PolicyLayer policy for myob_approval_deny. 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.

What MCP server provides myob_approval_deny? +

myob_approval_deny 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.