polymarket.trading.place_order
Place a limit order on Polymarket
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/polymarket.trading.place-order.md
What polymarket.trading.place_order does on Apibase
AI agents use polymarket.trading.place_order to commit financial operations through Apibase, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
side | string | Yes | Order side: buy or sell |
size | number | Yes | Order size in USDC units |
price | number | Yes | Limit price between 0.01 and 0.99 |
neg_risk | boolean | — | Whether this is a negative risk market |
token_id | string | Yes | Polymarket CLOB token ID to trade |
tick_size | string | — | Minimum price increment (e.g. 0.01, 0.001) |
order_type | string | — | Order type: Good-Til-Cancelled, Good-Til-Date, Fill-Or-Kill |
Parameters from the server's own tool schema.
Why polymarket.trading.place_order is rated Critical
Places financial orders on a prediction market, directly committing funds.
From the tool's definition Place a limit order on Polymarket
Attacks that exploit this kind of access
The rule that runs polymarket.trading.place_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For polymarket.trading.place_order, this is the rule to start with:
Any call to polymarket.trading.place_order is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every polymarket.trading.place_order call is checked against it from then on.
Questions about polymarket.trading.place_order
Place a limit order on Polymarket. It is categorised as a Financial tool in the Apibase MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
polymarket.trading.place_order accepts 7 parameters: side, size, price, neg_risk, token_id, tick_size, order_type. Required: side, size, price, token_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for polymarket.trading.place_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 Apibase. Nothing to install.
polymarket.trading.place_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the polymarket.trading.place_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 polymarket.trading.place_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.
polymarket.trading.place_order is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
Across the catalogue