astranl.com

The input schema includes a boolean field 'synthetic' with no description of its effect. Depending on backend behavior, this could be used to silently mark a task as a test/dummy while still triggering real-world coordination, or conversely allow an agent to disguise real transactions as synthetic (or vice versa) without visibility to the user. Lack of documentation on this field's semantics is a transparency risk for an agent that might set it incorrectly or be instructed to set it in a way that hides real financial/contractual actions from the user.

create_task registers a real execution task with budget_cents and triggers coordination with human/company/robot executors, incurring a coordination fee paid directly by the client. Given the ask_astranl tool explicitly advertises itself as 'read-only, nothing is created, contacted, or authorized' as a distinguishing feature, this implies create_task does authorize/contact real-world parties and commit real budgets. There is no schema-level requirement for an explicit user-confirmed authorization token before dispatch, so an agent could inadvertently create binding real-world tasks (spending money, contacting third parties) based on ambiguous or manipulated instructions.