Return known MYOB endpoint paths and write flow for an entity.
AI agents call myob_metadata_get_entity_schema to retrieve information from MYOB Codex MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema and endpoint metadata about entities without querying live business data or triggering any state changes. It is informational in nature, supporting the client in understanding available operations. The 'write flow' reference indicates it describes write operations rather than performing them. No data is created, modified, deleted, or executed — only structural information is returned.
From the tool's definition Tool name includes 'get' and description states 'Return known MYOB endpoint paths and write flow for an entity' — this is metadata retrieval with no side effects.
Attacks that exploit this kind of access
Return known MYOB endpoint paths and write flow for an entity. It is categorised as a Read tool in the MYOB Codex MCP MCP Server, which means it retrieves data without modifying state.
Register the MYOB Codex MCP server in PolicyLayer and add a rule for myob_metadata_get_entity_schema: 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_metadata_get_entity_schema is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the myob_metadata_get_entity_schema 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_metadata_get_entity_schema. 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_metadata_get_entity_schema 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 →