pm_merge_positions
Merge outcome token sets back to USDC collateral on CTF contract
This record as markdown: /tools/minhoyoo-iotrust-waiaas/pm-merge-positions.md
What pm_merge_positions does on Waiaas
AI agents use pm_merge_positions to commit financial operations through Waiaas, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why pm_merge_positions is rated Critical
This tool interacts with a Conditional Token Framework (CTF) contract to merge prediction market positions back into USDC collateral. This involves on-chain financial transactions that convert outcome tokens into real monetary value (USDC), constituting a financial operation. Misuse could result in loss of funds or unintended liquidation of market positions.
From the tool's definition Merge outcome token sets back to USDC collateral on CTF contract
Attacks that exploit this kind of access
The rule that runs pm_merge_positions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Waiaas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pm_merge_positions, this is the rule to start with:
Any call to pm_merge_positions is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Waiaas, apply this rule, and every pm_merge_positions call is checked against it from then on.
Questions about pm_merge_positions
Merge outcome token sets back to USDC collateral on CTF contract. It is categorised as a Financial tool in the Waiaas MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Waiaas MCP server in PolicyLayer and add a rule for pm_merge_positions: 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_merge_positions 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 pm_merge_positions 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_merge_positions. 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_merge_positions 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.
More on Waiaas, and thousands of servers like it.
Across the catalogue