Execute a deployed DataGen workflow with custom inputs. Use this to run pre-built workflows (like data processing pipelines, web scrapers, or automation scripts) that have been deployed as API endpoints. This starts an asynchronous execution - you'll get a run ID that you can monitor with 'checkR...
Part of the DataGen server.
Free to start. No card required.
AI agents use submitDeploymentRun to create or modify resources in DataGen. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call submitDeploymentRun repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach DataGen.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"submitDeploymentRun": {
"limits": [
{
"counter": "submitdeploymentrun_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full DataGen policy for all 20 tools.
These attack patterns abuse exactly the kind of access submitDeploymentRun gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Execute a deployed DataGen workflow with custom inputs. Use this to run pre-built workflows (like data processing pipelines, web scrapers, or automation scripts) that have been deployed as API endpoints. This starts an asynchronous execution - you'll get a run ID that you can monitor with 'checkRunStatus'. Typical workflow: 1. Use validateDeploymentConnection tool to validate the deployment and get the missing MCP or Secrets. 2. Use this tool to start a deployment 3. Get a run_uuid in response 4. Use checkRunStatus to monitor progress 5. Retrieve results when complete Use cases: Run data pipelines, execute scrapers, trigger automations, process files. Error handling: If found any missing MCP or Secrets, try to run validate deployment connection tool to validate the deployment and get the missing MCP or Secrets.. It is categorised as a Write tool in the DataGen MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DataGen MCP server in PolicyLayer and add a rule for submitDeploymentRun: 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 DataGen. Nothing to install.
submitDeploymentRun is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submitDeploymentRun 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 submitDeploymentRun. 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.
submitDeploymentRun is provided by the DataGen MCP server (kuoyusheng/datagendev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 DataGen tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.