hatchloop.dev

This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.

Several fields (top-level description, 'on_behalf_of', 'business_id', 'message_type') are truncated mid-sentence with '…'. E.g. 'on_behalf_of' ends with 'On WhatsApp this opens a…' and 'business_id' ends with 'Enables global demand shaping…'. The agent cannot verify what these fields actually do or whether the truncated portion contains further behavioral instructions. Recommend obtaining full field descriptions before trusting these parameters, especially any that claim to change routing/consent/demand behavior.

Description ends with 'Use it to de-risk a paid send the same way check_booking_link…' referencing a tool not present in this list, and is cut off. This is likely benign but the dangling reference to an unlisted tool ('check_booking_link') should be verified to ensure no confusion or spoofing risk.

The 'data' field description is truncated ('e.g., {otp_code} for otp, {appointment_time, smb_name}…'), leaving the full schema for type-specific payloads unclear. Not a security risk per se, but worth confirming the full field list doesn't include free-text injection vectors that bypass the compliance gate used by send_message.