myob_attachment_prepare_upload

WHAT IT DOES

What myob_attachment_prepare_upload does on MYOB Codex MCP

AI agents use myob_attachment_prepare_upload 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_attachment_prepare_upload needs a policy

This tool prepares an upload by staging content_base64 in a pending payload. It does not immediately commit the attachment but stores it pending approval, making it a reversible write operation. The staged data can presumably be cancelled or modified before approval is granted.

From the tool's definition Tool description states 'Prepare attachment upload' and 'content_base64 is stored in the pending payload until approved', indicating it creates/stages data (an attachment) that persists until approval, consistent with Write operations that create or modify…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

myob_attachment_prepare_upload Rate-limited

myob_attachment_prepare_upload 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_attachment_prepare_upload": {
      "limits": [
        {
          "counter": "myob_attachment_prepare_upload_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_attachment_prepare_upload

What does the myob_attachment_prepare_upload tool do? +

Prepare attachment upload. content_base64 is stored in the pending payload until approved. 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_attachment_prepare_upload? +

Register the MYOB Codex MCP server in PolicyLayer and add a rule for myob_attachment_prepare_upload: 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_attachment_prepare_upload? +

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

Can I rate-limit myob_attachment_prepare_upload? +

Yes. Add a rate_limit block to the myob_attachment_prepare_upload 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_attachment_prepare_upload completely? +

Set action: deny in the PolicyLayer policy for myob_attachment_prepare_upload. 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_attachment_prepare_upload? +

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