positions.check_exits
Scan all open positions for exit conditions: market resolution, stop-loss/take-profit triggers, or the original trader exiting. Updates P&L and closes positions that meet exit criteria. No parameters needed.
This record as markdown: /tools/demwick-polymarket-agent-mcp/positions.check-exits.md
What positions.check_exits does on Polymarket Agent Mcp
AI agents use positions.check_exits to commit financial operations through Polymarket Agent Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why positions.check_exits is rated Critical
Closing trading positions is a financial action that commits or finalizes financial outcomes. The tool can automatically exit positions (selling assets) based on triggered conditions, which directly affects financial holdings. The server context of 'live trades via the CLOB API' confirms real money is involved.
From the tool's definition 'closes positions that meet exit criteria' and 'Updates P&L' — this tool automatically closes live trading positions on Polymarket based on exit conditions including stop-loss/take-profit triggers
Attacks that exploit this kind of access
The rule that runs positions.check_exits 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 positions.check_exits, this is the rule to start with:
Any call to positions.check_exits is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Polymarket Agent Mcp, apply this rule, and every positions.check_exits call is checked against it from then on.
Questions about positions.check_exits
Scan all open positions for exit conditions: market resolution, stop-loss/take-profit triggers, or the original trader exiting. Updates P&L and closes positions that meet exit criteria. No parameters needed. It is categorised as a Financial tool in the Polymarket Agent Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Polymarket Agent MCP server in PolicyLayer and add a rule for positions.check_exits: 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.
positions.check_exits 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 positions.check_exits 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 positions.check_exits. 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.
positions.check_exits 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.
Across the catalogue