AI agents invoke createTestDataGenerator to trigger actions in Azure Devops. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool generates test data, which implies executing some form of code or process to produce and likely write data artifacts. It goes beyond a simple read/query and involves creating/generating data programmatically. Classified as Execute due to the active generation process, with Write being a close secondary consideration.
From the tool's definition Generate test data for automated tests
Documented attack patterns abuse exactly the kind of access createTestDataGenerator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Azure Devops, and nothing reaches the server without passing your rules. This is the rule we recommend for createTestDataGenerator:
{
"version": "1",
"default": "deny",
"tools": {
"createTestDataGenerator": {
"limits": [
{
"counter": "createtestdatagenerator_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}createTestDataGenerator stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate test data for automated tests. It is categorised as a Execute tool in the Azure Devops MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Azure Devops MCP server in PolicyLayer and add a rule for createTestDataGenerator: 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 Azure Devops. Nothing to install.
createTestDataGenerator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the createTestDataGenerator 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 createTestDataGenerator. 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.
createTestDataGenerator is provided by the Azure Devops MCP server (ryancardin15/azuredevops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 97 Azure Devops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
97 Azure Devops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.