order_history

Fetch order history.

SERVERIndodax MCP Server SOURCEadhinugroho1711/mcp-indodax

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adhinugroho1711-mcp-indodax/order-history.md

WHAT IT DOES

What order_history does on Indodax MCP Server

AI agents call order_history 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.

RISK

Why order_history is rated Low

This tool queries historical trading data and returns information about past orders. 'Fetch' is a read operation that does not modify, delete, or execute any actions. While the server as a whole manages financial trading accounts, this specific tool only retrieves existing historical data without moving money or committing financial obligations.

From the tool's definition Tool name 'order_history' and description 'Fetch order history' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs order_history 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 order_history, this is the rule to start with:

order_history Allowed

order_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "order_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Indodax MCP Server, apply this rule, and every order_history call is checked against it from then on.

FAQ

Questions about order_history

What does the order_history tool do? +

Fetch order history. It is categorised as a Read tool in the Indodax MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on order_history? +

Register the Indodax MCP Server MCP server in PolicyLayer and add a rule for order_history: 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.

What risk level is order_history? +

order_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit order_history? +

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

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

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

KEEP EXPLORING

More on Indodax MCP Server, and thousands of servers like it.

This server

All 22 Indodax MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →