oms_get_order
Use this to load full detail on one order including all execution
This record as markdown: /tools/8vdx1-fundos-mcp/oms-get-order.md
What oms_get_order does on Fundos
AI agents call oms_get_order to retrieve information from Fundos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why oms_get_order is rated Low
This tool queries and retrieves existing order data from an Order Management System. The verb 'load' and 'get' indicate a read-only retrieval operation. There is no indication of order creation, modification, execution, or cancellation.
From the tool's definition Tool name 'oms_get_order' with description 'load full detail on one order including all execution' — retrieves order information without modifying or executing trades.
Attacks that exploit this kind of access
The rule that runs oms_get_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_get_order, this is the rule to start with:
oms_get_order is read-only, so it stays allowed. 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_get_order call is checked against it from then on.
Questions about oms_get_order
Use this to load full detail on one order including all execution. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.
Register the Fundos MCP server in PolicyLayer and add a rule for oms_get_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_get_order 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 oms_get_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_get_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_get_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.
This server
Across the catalogue