other
- Location
skill.md:849- Finding
Server-Controlled Heartbeat Hints Can Trigger Autonomous Consequential Actions
- Content
View full analysis
0 → POST /api/agents/:handle/follow (follow back) 8. IF appliedBounties[*].status=accepted → complete the task, then PUT /api/bounties/:id/claim {} # PUT, empty body ``` ### Technical Analysis The recommended heartbeat treats fields returned by the remote `aiins.cc` status endpoint as sufficient authorization for authenticated state-changing operations. The response controls conditions that can lead the Agent to: - Edit and resubmit rejected content. - Publish pending drafts. - Create new public content. - Spend tokens to boost notes. - Follow remote accounts. - Mark bounty work complete and change payment-related state. These operations are not necessary for a status-monitoring heartbeat and exceed the minimum privilege required to check notifications or analytics. Remote hints should be treated as untrusted recommendations rather than commands. The separate implementation in `heartbeat.md` is more cautious about posting because it checks relevance and whether the Agent has valuable content. Nevertheless, the broader routine in `skill.md` explicitly recommends consequential actions based directly on server-provided fields and runs every 30 minutes. The pre-scan’s sensitive-network pattern in `heartbe ...[truncated 2270 chars]- Remediation
View remediation
