runway_get_task
Check the status of a Runway ML generation task. Returns status, progress, and video URL when complete.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/runway-get-task.md
What runway_get_task does on UnClick
AI agents call runway_get_task to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | Runway API key |
task_id | string | Yes | Task ID returned by runway_generate_video |
Parameters from the server's own tool schema.
Why runway_get_task is rated Low
This tool queries the state of an existing generation task and returns data without causing side effects. It is a read-only operation that retrieves status information about a previously-initiated task. No data is created, modified, deleted, or executed as a result of calling this tool.
From the tool's definition Tool description states it 'Check the status' and 'Returns status, progress, and video URL' — purely retrieves task information with no modification, deletion, or execution of operations.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs runway_get_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runway_get_task, this is the rule to start with:
runway_get_task is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every runway_get_task call is checked against it from then on.
Questions about runway_get_task
Check the status of a Runway ML generation task. Returns status, progress, and video URL when complete. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
runway_get_task accepts 2 parameters: api_key, task_id. Required: api_key, task_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for runway_get_task: 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 UnClick. Nothing to install.
runway_get_task 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 runway_get_task 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 runway_get_task. 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.
runway_get_task is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue