oms_create_order
Use this to submit a new equity order through the OMS when
This record as markdown: /tools/8vdx1-fundos-mcp/oms-create-order.md
What oms_create_order does on Fundos
AI agents invoke oms_create_order to trigger actions in Fundos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why oms_create_order is rated High
Submitting an order through an OMS triggers an external financial operation (placing a trade order) whose effects depend on the arguments (ticker, quantity, side, etc.). While it may not immediately move money, it initiates a binding trade instruction in financial markets.
From the tool's definition 'submit a new equity order through the OMS' — triggers an external order management system operation to place an equity order
Attacks that exploit this kind of access
The rule that runs oms_create_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For oms_create_order, this is the rule to start with:
oms_create_order stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fundos, apply this rule, and every oms_create_order call is checked against it from then on.
Questions about oms_create_order
Use this to submit a new equity order through the OMS when. It is categorised as a Execute tool in the Fundos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fundos MCP server in PolicyLayer and add a rule for oms_create_order: 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 Fundos. Nothing to install.
oms_create_order is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the oms_create_order 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 oms_create_order. 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.
oms_create_order is provided by the Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fundos, and thousands of servers like it.
Across the catalogue