get_workflow_status
Poll this between steps: returns active + recently-finished AI jobs (scope by project_id, or style_id for style analysis), plus per-segment- asset render statuses for projects. A step is done when its jobs reach status=complete (or error, with a user-readable message). NOTE: finished jobs drop ou...
This record as markdown: /tools/com-framesail-framesail/get-workflow-status.md
What get_workflow_status does on Framesail
AI agents call get_workflow_status to retrieve information from Framesail 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 |
|---|---|---|---|
style_id | string | — | Style ID to scope jobs to (style analysis); pass exactly one of project_id or style_id |
project_id | string | — | Project ID to scope jobs to; pass exactly one of project_id or style_id |
Parameters from the server's own tool schema.
Why get_workflow_status is rated Low
This is a pure query/status-checking tool. It retrieves information about job and render states without modifying data, triggering new operations, or causing side effects. The guidance to 'Prefer await_jobs over polling this in a tight loop' confirms it is a passive observation mechanism, not an action trigger. While it monitors long-running operations, it does not execute them—it only reports their status.
From the tool's definition Returns active + recently-finished AI jobs and segment asset render statuses; explicitly described as polling/querying operation with no state modification. Key phrases: 'Poll this between steps', 'returns', 'per-segment-asset render statuses'.
Attacks that exploit this kind of access
The rule that runs get_workflow_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_workflow_status, this is the rule to start with:
get_workflow_status 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 Framesail, apply this rule, and every get_workflow_status call is checked against it from then on.
Questions about get_workflow_status
Poll this between steps: returns active + recently-finished AI jobs (scope by project_id, or style_id for style analysis), plus per-segment- asset render statuses for projects. A step is done when its jobs reach status=complete (or error, with a user-readable message). NOTE: finished jobs drop out of jobs after ~30s — a short list does NOT mean work was lost; judge render batches by segment_assets statuses (or get_pipeline_progress), never by counting jobs. Prefer await_jobs over polling this in a tight loop. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
get_workflow_status accepts 2 parameters: style_id, project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for get_workflow_status: 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 Framesail. Nothing to install.
get_workflow_status 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 get_workflow_status 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 get_workflow_status. 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.
get_workflow_status is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue