Wait for an async job to finish and return its result in ONE call — no manual polling loop. Pass the requestId + jobType from an async tool (generate_video, animate_image, generate_3d_model, transcribe_audio, epub_to_audiobook, ai_call). If your MCP client opened the request with 'Accept: text/ev...
AI agents call await_result to retrieve information from Sats4AI - Bitcoin-Powered AI Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
jobType | string | Yes | Must match the async tool that returned requestId. |
requestId | string | Yes | The requestId returned by the async tool. |
Parameters from the server's own tool schema.
This tool purely retrieves the result of a previously submitted async job. It performs polling/status checks and returns data without creating, modifying, executing, or destroying anything. It is a read/fetch operation only.
From the tool's definition Wait for an async job to finish and return its result — no manual polling loop... does a single status check and returns immediately... returns final result
Attacks that exploit this kind of access
Wait for an async job to finish and return its result in ONE call — no manual polling loop. Pass the requestId + jobType from an async tool (generate_video, animate_image, generate_3d_model, transcribe_audio, epub_to_audiobook, ai_call). If your MCP client opened the request with 'Accept: text/event-stream', this streams live progress (notifications/progress) while it waits, then returns the final result; otherwise it does a single status check and returns immediately (call again until status='COMPLETED'). For long jobs it waits up to ~4 minutes per call, then returns status='IN_PROGRESS' with timed_out=true — call again with the same requestId to keep waiting. Equivalent to check_job_status + get_job_result combined. Free; no payment. It is categorised as a Read tool in the Sats4AI - Bitcoin-Powered AI Tools MCP Server, which means it retrieves data without modifying state.
await_result accepts 2 parameters: jobType, requestId. Required: jobType, requestId. The full parameter table on this page comes from the server's own tool schema.
Register the Sats4AI - Bitcoin-Powered AI Tools MCP server in PolicyLayer and add a rule for await_result: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Sats4AI - Bitcoin-Powered AI Tools. Nothing to install.
await_result is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the await_result rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for await_result. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
await_result is provided by the Sats4AI - Bitcoin-Powered AI Tools MCP server (cnghockey/sats4ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →