Query the status and result of a Flux image generation task. Use this to check if a generation is complete and retrieve the resulting image URLs and metadata. Use this when: - You want to check if an image generation has completed - You need to retrieve image URLs from a pre...
Part of the Mcp Flux Pro MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call flux_get_task to retrieve information from Mcp Flux Pro without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though flux_get_task only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
flux_get_task:
rules:
- action: allowSee the full Mcp Flux Pro policy for all 6 tools.
Agents calling read-class tools like flux_get_task have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Query the status and result of a Flux image generation task. Use this to check if a generation is complete and retrieve the resulting image URLs and metadata. Use this when: - You want to check if an image generation has completed - You need to retrieve image URLs from a previous generation - You used async callback and want to check results later - The initial generation returned a task_id without immediate results Returns: Task status and generation result including image URLs. . It is categorised as a Read tool in the Mcp Flux Pro MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for flux_get_task. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Flux Pro MCP server.
flux_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 flux_get_task rule in your Intercept 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 Intercept policy for flux_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.
flux_get_task is provided by the Mcp Flux Pro MCP server (acedatacloud-mcp/mcp-flux-pro). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept