Tool Parameter Abuse
- Category
- Tool Misuse
- Confidence
- 60% confidence
- Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
- Content
md ir own shell or agent config (for example `export OPENCLAW_LAUNCH_API_KEY=...`). Do not ask them to paste the key into the chat, and do not write it into any file yourself. - Recommend a dedicated key even if the user already has one. A key can only see and control the bots that same key created, so an agent-only key cannot reach bots made by the user's storefront or other keys, and revoking it never disrupts them. It does share the account's balance, plan limits and model funding (see "What a key can cost"). - Never print, echo, log or summarize the key, never write it to a file, a commit, an issue or a bot message, never send it to any host other than `openclawlaunch.com`, and never run these commands with `set -x`, `curl -v` or `--trace`. Every call sends the key the same way: `printf` writes the header into curl's config on stdin (`-K -`), so the key never appears in your command text or in curl's process arguments. `-q` comes first so a local `.curlrc` cannot change the request.
