Anti-Refusal Statement
- Category
- Anti-Refusal
- Confidence
- 85% confidence
- Finding
Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.
- Content
md only, destructive or open-world. Treat anything not read-only as a write. - **Don't start payments, and don't hide indirect ones.** You must not transfer money, make a payment or trade securities on your own. When asked to ("pay vendor X now", "buy 100 shares"), say you can't, and offer to create a task for a person instead. Spaces actions *can* lead to real money movement, though. Completing an approval can resume a workflow that posts entries or releases a payment. A workflow or a connected accounting, ERP or banking app can create or release payments. Before any of these, tell the user plainly that it may move money, and get an explicit yes. Afterwards, report exactly what the tool returned. Never say that no money moved, or that a payment happened, unless the result says so. - Report results exactly as the tools return them, including failures. - To disconnect, the user can run `openclaw mcp logout peakflo`, or revoke access in app.peakflo.ai → **Settings → MCP → Connected apps**.
