Start an orchestration run by posting a task to the Bernstein server. Args: goal: Description of what you want Bernstein to accomplish. role: Specialist role to assign (backend, frontend, qa, security, …). priority: 1=critical, 2=normal, 3=nice-to-have. scope: Task scope - small, medium, or large...
AI agents invoke bernstein_run to trigger actions in Bernstein - Multi-agent orchestration. 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 initiates automated workflows controlled by multiple AI coding agents. It executes arbitrary tasks specified by the user and delegates work to external agents whose behavior depends on the provided goal and role parameters. While the effects are intended to be reversible (software development tasks), the tool itself triggers unbounded code execution through agent orchestration, making it Execute category.
From the tool's definition Tool 'Start an orchestration run by posting a task to the Bernstein server' executes multi-agent orchestration workflows that automate software development.
Documented attack patterns abuse exactly the kind of access bernstein_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bernstein - Multi-agent orchestration, and nothing reaches the server without passing your rules. This is the rule we recommend for bernstein_run:
{
"version": "1",
"default": "deny",
"tools": {
"bernstein_run": {
"limits": [
{
"counter": "bernstein_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}bernstein_run 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.
Start an orchestration run by posting a task to the Bernstein server. Args: goal: Description of what you want Bernstein to accomplish. role: Specialist role to assign (backend, frontend, qa, security, …). priority: 1=critical, 2=normal, 3=nice-to-have. scope: Task scope - small, medium, or large. complexity: Task complexity - low, medium, or high. estimated_minutes: Rough time estimate in minutes. Returns: JSON with the created task ID, title, and status. It is categorised as a Execute tool in the Bernstein - Multi-agent orchestration MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bernstein - Multi-agent orchestration MCP server in PolicyLayer and add a rule for bernstein_run: 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 Bernstein - Multi-agent orchestration. Nothing to install.
bernstein_run 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 bernstein_run 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 bernstein_run. 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.
bernstein_run is provided by the Bernstein - Multi-agent orchestration MCP server (sipyourdrink-ltd/bernstein). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Bernstein - Multi-agent orchestration tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Bernstein - Multi-agent orchestration tools catalogued and risk-classified — across an index of 42,500+ MCP servers.