AI agents invoke test_workflow to trigger actions in Automatisch MCP Server. 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.
Testing a workflow involves actually running or simulating it with sample data, which constitutes an Execute action. The blast radius is medium because while it uses sample data, the workflow execution could trigger real side effects depending on the workflow's actions (e.g., sending emails, calling APIs, writing to databases).
From the tool's definition 'Test a workflow with sample data' — triggers execution of a workflow, which constitutes running an external operation
Documented attack patterns abuse exactly the kind of access test_workflow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automatisch MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for test_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"test_workflow": {
"limits": [
{
"counter": "test_workflow_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}test_workflow 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.
Test a workflow with sample data. It is categorised as a Execute tool in the Automatisch MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Automatisch MCP Server MCP server in PolicyLayer and add a rule for test_workflow: 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 Automatisch MCP Server. Nothing to install.
test_workflow 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 test_workflow 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 test_workflow. 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.
test_workflow is provided by the Automatisch MCP Server MCP server (milisp/automatisch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automatisch MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Automatisch MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.