This record as markdown: /tools/adhinugroho1711-mcp-indodax/get-order.md
What get_order does on Indodax MCP Server
AI agents call get_order to retrieve information from Indodax MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_order is rated Low
This tool retrieves information about an existing order using its ID as a parameter. It performs a query operation without creating, modifying, deleting, or executing any orders. While it accesses trading account data (which could be considered sensitive), the act itself is read-only retrieval with no capability to change state or trigger financial transactions.
From the tool's definition Tool name 'get_order' combined with description 'Get order by its numeric ID' indicates a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Indodax MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_order, this is the rule to start with:
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 Indodax MCP Server, apply this rule, and every get_order call is checked against it from then on.
Questions about get_order
Get order by its numeric ID. It is categorised as a Read tool in the Indodax MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Indodax MCP Server MCP server in PolicyLayer and add a rule for 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 Indodax MCP Server. Nothing to install.
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 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 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.
get_order is provided by the Indodax MCP Server MCP server (adhinugroho1711/mcp-indodax). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Indodax MCP Server, and thousands of servers like it.
This server
Across the catalogue