Low Risk

get_orders

Get order history.

How to control get_orders ↓

What get_orders does on Fyers MCP Server

AI agents call get_orders to retrieve information from Fyers MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_orders needs a policy

This tool retrieves past order information from the Fyers trading platform without modifying, executing, or affecting any financial transactions. It is purely informational, examining existing data rather than creating, modifying, or deleting records. The blast radius of misuse is minimal—an attacker could only view order history, not place trades or move funds.

From the tool's definition Tool name 'get_orders' and description 'Get order history' indicate a retrieval operation with no side effects. The verb 'Get' and context of querying historical data confirms this is a read-only action.

Documented attack patterns abuse exactly the kind of access get_orders gives an agent:

How to control get_orders

PolicyLayer is an MCP gateway — it sits between your AI agents and Fyers MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_orders:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_orders": {}
  }
}

get_orders is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Fyers MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_orders

What does the get_orders tool do? +

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

How do I enforce a policy on get_orders? +

Register the Fyers MCP Server MCP server in PolicyLayer and add a rule for get_orders: 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 Fyers MCP Server. Nothing to install.

What risk level is get_orders? +

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

Can I rate-limit get_orders? +

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

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

get_orders is provided by the Fyers MCP Server MCP server (quantabox/fyers-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fyers MCP Server tool call.

Start from Fyers MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 Fyers MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.