Monitor the progress and results of a running DataGen workflow with automatic polling. After starting a workflow with 'submitDeploymentRun', use this to check if it's still running, completed successfully, or failed. Provide a run UUID directly, or supply a deployment UUID to automatically loc...
Part of the DataGen MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call checkRunStatus to retrieve information from DataGen 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 checkRunStatus 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:
checkRunStatus:
rules:
- action: allowSee the full DataGen policy for all 20 tools.
Agents calling read-class tools like checkRunStatus 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.
Monitor the progress and results of a running DataGen workflow with automatic polling. After starting a workflow with 'submitDeploymentRun', use this to check if it's still running, completed successfully, or failed. Provide a run UUID directly, or supply a deployment UUID to automatically locate the most recent run for that deployment. **Status types:** - 'pending': Waiting in queue, check again in a few seconds - 'running': Still executing, check again in a few seconds - 'completed': Finished successfully, output data available - 'failed': Execution failed, error details provided **Controls:** - 'timeout_seconds' (default 180, max 600) to cap how long to poll - 'poll_interval_seconds' (default 5, min 2, max 30) between checks **Lookup options:** - Provide 'run_uuid' for direct status polling - Provide 'deployment_uuid' to look up the latest run automatically. It is categorised as a Read tool in the DataGen MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for checkRunStatus. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the DataGen MCP server.
checkRunStatus 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 checkRunStatus 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 checkRunStatus. 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.
checkRunStatus is provided by the DataGen MCP server (kuoyusheng/datagendev). 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