pm_split_position
Split USDC collateral into outcome token sets on CTF contract
This record as markdown: /tools/minhoyoo-iotrust-waiaas/pm-split-position.md
What pm_split_position does on Waiaas
AI agents use pm_split_position to commit financial operations through Waiaas, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why pm_split_position is rated Critical
This tool moves USDC collateral into a prediction market CTF (Conditional Token Framework) contract, committing real financial assets into on-chain positions. It involves actual crypto asset operations and financial commitment, placing it firmly in the Financial category. Severity is high because misuse could lock or mis-allocate user funds into incorrect market positions on-chain.
From the tool's definition Split USDC collateral into outcome token sets on CTF contract
Attacks that exploit this kind of access
The rule that runs pm_split_position 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_split_position, this is the rule to start with:
Any call to pm_split_position 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_split_position call is checked against it from then on.
Questions about pm_split_position
Split USDC collateral into outcome token sets 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_split_position: 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_split_position 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_split_position 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_split_position. 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_split_position 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