orders.status
Check the live state of a specific Polymarket limit order by its order_id. Use after orders.buy, orders.batch, or wta.bid to track fill progress, or to verify that an orders.cancel call succeeded. Returns the order status (OPEN, FILLED, CANCELLED, or EXPIRED), filled amount, remaining size, curre...
This record as markdown: /tools/demwick-polymarket-agent-mcp/orders.status.md
What orders.status does on Polymarket Agent Mcp
AI agents call orders.status to retrieve information from Polymarket Agent Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why orders.status is rated Low
This tool only retrieves and returns status information about an existing order. It does not create, modify, cancel, or execute anything — it is a pure read/query operation. Severity is low as misuse only exposes order status data.
From the tool's definition Check the live state of a specific Polymarket limit order... Returns the order status (OPEN, FILLED, CANCELLED, or EXPIRED), filled amount, remaining size, current limit price
Attacks that exploit this kind of access
The rule that runs orders.status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Polymarket Agent Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For orders.status, this is the rule to start with:
orders.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 Polymarket Agent Mcp, apply this rule, and every orders.status call is checked against it from then on.
Questions about orders.status
Check the live state of a specific Polymarket limit order by its order_id. Use after orders.buy, orders.batch, or wta.bid to track fill progress, or to verify that an orders.cancel call succeeded. Returns the order status (OPEN, FILLED, CANCELLED, or EXPIRED), filled amount, remaining size, current limit price, and the market it was placed on. Obtain the order_id from the response of the placing tool or from orders.list. Only works in live mode. It is categorised as a Read tool in the Polymarket Agent Mcp MCP Server, which means it retrieves data without modifying state.
Register the Polymarket Agent MCP server in PolicyLayer and add a rule for orders.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 Polymarket Agent Mcp. Nothing to install.
orders.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 orders.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 orders.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.
orders.status is provided by the Polymarket Agent MCP server (demwick/polymarket-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Polymarket Agent, and thousands of servers like it.
This server
Across the catalogue