This record as markdown: /tools/launch-on-basis-mcp-ts/pm-finalize.md
What pm_finalize does on Basis MCP Server
AI agents use pm_finalize to commit financial operations through Basis MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why pm_finalize is rated Critical
Finalizing a prediction market is a financial operation that locks in outcomes and triggers irreversible settlement of funds. Misuse could result in unintended financial transfers, market manipulation, or loss of user assets. This ranks higher than Execute or Destructive because it specifically commits financial obligations and moves value.
From the tool's definition Tool finalizes a private market, which commits financial outcomes and likely distributes funds based on prediction market results. Part of a suite including 'bet', 'buy_token', 'buy_order', and staking/loan functionality on BNB Smart Chain.
Attacks that exploit this kind of access
The rule that runs pm_finalize safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pm_finalize, this is the rule to start with:
Any call to pm_finalize is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every pm_finalize call is checked against it from then on.
Questions about pm_finalize
Finalize a private market. It is categorised as a Financial tool in the Basis MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for pm_finalize: 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 Basis MCP Server. Nothing to install.
pm_finalize 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_finalize 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_finalize. 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_finalize is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
Across the catalogue