get_order_status
Get the status of a specific order.
This record as markdown: /tools/abhijeetmohanan-growwmcp/get-order-status.md
What get_order_status does on Groww MCP Server
AI agents call get_order_status to retrieve information from Groww 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_status is rated Low
This tool retrieves status information about an existing order. It performs no side effects, does not create, modify, or delete data, and does not execute trades or move funds. The action is a simple data retrieval (get), making it a Read category tool.
From the tool's definition Tool name 'get_order_status' and description 'Get the status of a specific order' indicate a read-only query operation that retrieves order information without modifying any state.
Attacks that exploit this kind of access
The rule that runs get_order_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Groww 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_status, this is the rule to start with:
get_order_status 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 Groww MCP Server, apply this rule, and every get_order_status call is checked against it from then on.
Questions about get_order_status
Get the status of a specific order. It is categorised as a Read tool in the Groww MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Groww MCP Server MCP server in PolicyLayer and add a rule for get_order_status: 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 Groww MCP Server. Nothing to install.
get_order_status 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_status 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_status. 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_status is provided by the Groww MCP Server MCP server (abhijeetmohanan/growwmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Groww MCP Server, and thousands of servers like it.
This server
Across the catalogue