markets.watch
Manage your market watchlist: add, remove, or list watched markets with optional price alert thresholds. When a market crosses your alert price, it shows up in check_exits.
This record as markdown: /tools/demwick-polymarket-agent-mcp/markets.watch.md
What markets.watch does on Polymarket Agent Mcp
AI agents use markets.watch to create or update resources in Polymarket Agent Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Polymarket Agent Mcp environment.
Why markets.watch is rated Medium
This tool creates and modifies a personal watchlist (add/remove markets, set alert thresholds). It writes configuration/preference data reversibly — markets can be added or removed freely. While it doesn't directly execute trades or move money, misconfigured alerts could indirectly trigger downstream financial actions via check_exits. The primary action is a reversible write to a watchlist data structure.
From the tool's definition Manage your market watchlist: add, remove, or list watched markets with optional price alert thresholds
Attacks that exploit this kind of access
The rule that runs markets.watch 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 markets.watch, this is the rule to start with:
markets.watch stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 markets.watch call is checked against it from then on.
Questions about markets.watch
Manage your market watchlist: add, remove, or list watched markets with optional price alert thresholds. When a market crosses your alert price, it shows up in check_exits. It is categorised as a Write tool in the Polymarket Agent Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Polymarket Agent MCP server in PolicyLayer and add a rule for markets.watch: 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.
markets.watch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the markets.watch 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 markets.watch. 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.
markets.watch 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