polymarket_fill_risk · Mcp Celestrak MCP: Risk & Policy

Q: What does the polymarket_fill_risk tool do?

Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of market (single-market mode) or event (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L). It is categorised as a Financial tool in the Mcp Celestrak MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

Q: What parameters does polymarket_fill_risk accept?

polymarket_fill_risk accepts 4 parameters: side, event, market, size_usd. The full parameter table on this page comes from the server's own tool schema.

Q: How do I enforce a policy on polymarket_fill_risk?

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

Q: What risk level is polymarket_fill_risk?

polymarket_fill_risk is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Q: Can I rate-limit polymarket_fill_risk?

Yes. Add a rate_limit block to the polymarket_fill_risk 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.

Q: How do I block polymarket_fill_risk completely?

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

Q: What MCP server provides polymarket_fill_risk?

polymarket_fill_risk is provided by the Mcp Celestrak MCP server (pipeworx-io/mcp-celestrak). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

WHAT IT DOES

What polymarket_fill_risk does on Mcp Celestrak

AI agents use polymarket_fill_risk to commit financial operations through Mcp Celestrak — usually the final step of a payment, billing, or trading workflow. A call moves real money.

PARAMETERS

Parameter	Type	Required	Description
`side`	string	—	Single-market: buy_yes \| sell_yes \| buy_no \| sell_no (default buy_yes). Basket: sell_yes \| buy_yes (default auto — sell if partition sum > 1, buy if < 1).
`event`	string	—	Basket mode: event slug or full polymarket.com URL — checks every leg of the partition.
`market`	string	—	Single-market mode: market slug or full polymarket.com URL.
`size_usd`	number	—	Single-market: USD to spend (buys) or target proceeds (sells). Basket: settlement notional — shares per leg, each paying $1 at resolution. Default 1000, clamp 1

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why polymarket_fill_risk needs a policy

This tool interacts with live prediction market order books (Polymarket CLOB), analyzes fill prices, slippage, and edge capture across market legs. While described as a 'check' or analysis tool, it references live order-book interaction and fill simulation that could trigger or inform real financial trades on a prediction market.

From the tool's definition polymarket_fill_risk, CLOB order-book depth, vwap_fill_price, slippage_pp, max_fillable_usd, sell every leg, capture overround

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Questions about polymarket_fill_risk

What does the polymarket_fill_risk tool do? +

Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of market (single-market mode) or event (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L). It is categorised as a Financial tool in the Mcp Celestrak MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does polymarket_fill_risk accept? +

polymarket_fill_risk accepts 4 parameters: side, event, market, size_usd. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on polymarket_fill_risk? +

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

What risk level is polymarket_fill_risk? +

polymarket_fill_risk is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit polymarket_fill_risk? +

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

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

polymarket_fill_risk is provided by the Mcp Celestrak MCP server (pipeworx-io/mcp-celestrak). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.