Update price or size of an active Polymarket order (cancel + replace)
AI agents use pm_update_order to create or update resources in Waiaas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Waiaas environment.
This is a Write operation because it modifies reversible data (market order parameters). It is not Destructive because the original order is cancelled and replaced rather than permanently purged without recovery option.
From the tool's definition Tool updates an active Polymarket order by modifying price or size (cancel + replace operation), which creates a new order state and modifies existing financial positions reversibly.
Documented attack patterns abuse exactly the kind of access pm_update_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for pm_update_order:
{
"version": "1",
"default": "deny",
"tools": {
"pm_update_order": {
"limits": [
{
"counter": "pm_update_order_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pm_update_order 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.
Free to start. No card required.
Update price or size of an active Polymarket order (cancel + replace). It is categorised as a Write tool in the Waiaas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Waiaas MCP server in PolicyLayer and add a rule for pm_update_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 Waiaas. Nothing to install.
pm_update_order 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 pm_update_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 pm_update_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.
pm_update_order is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waiaas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.