Tool Parameter Abuse
- Category
- Tool Misuse
- Confidence
- 80% 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
-d '{ "ids": ["POST_ID_1", "POST_ID_2"] }'
text Returns `200` (not 201) with `{ "deletedIds": [...], "notFoundIds": [...] }`. `notFoundIds` holds ids that don't exist or belong to another workspace; a repeated id is reported once, and repeating the same call is harmless. `ids` takes 1-100 UUIDs: `[]` returns `400` "At least one id is required", more than 100 returns `400` "ids cannot exceed 100 entries", a non-UUID returns `400` "Each id must be a valid UUID". One call counts as one request against this endpoint's own limit, separate from `DELETE /social-posts/:id`. **Delete everything that matches a filter** (for example every scheduled post on one account, after the user confirmed): don't advance `page` while deleting, because later posts shift onto pages you have already read and get skipped. Instead repeat: read `GET /social-posts?socialMediaIds=ACCOUNT_ID&statuses=SCHEDULED&page=0&limit=50`, send the returned ids to `POST /social-posts/bulk-delete`, and stop when `data` comes back empty. Stop on any error too; after a `429`, wait `Retry-After` seconds, then run the loop again.
