Sume MCP script_run: timeout 5 to 55 seconds, max_paid_calls brake

script_run in the hosted Sume MCP runs JavaScript with sume.call, a 5 to 55 second timeout and call limits, and journals every call and job it started.

5 min readSume
All posts

script_run executes JavaScript against the Sume tools through sume.call(name, args). timeout_seconds accepts 5 to 55, max_calls bounds total tool calls and max_paid_calls bounds the paid ones. The result carries a journal with calls[] and jobs[], so you can see what ran and which jobs are still going.

Use it when one agent turn would otherwise spend many round trips on a batch, for example listing a catalog and generating a handful of images. Set max_paid_calls low so a loop cannot run away.

Limits

script_run controls per Sume docs (read 2026-10-03)
ControlValueEffect
timeout_seconds5 to 55Script wall time
max_callsYou setTotal sume.call count
max_paid_callsYou setPaid calls only
journalcalls[] and jobs[]Audit trail of the run

Rules still apply

Paid calls inside a script still need idempotency_key. Jobs started in a script may outlive it, so finish with jobs_wait (55 second maximum hold) in a later call.

Sources

Related posts

More in Integrations

All Integrations posts

Written by Sume