Aggregate the status of all tasks of a running scenario. Args: orchestration_id: Value returned by bernstein_scenario. Returns: JSON with status counts and per-task details.
AI agents call bernstein_scenario_status to retrieve information from Bernstein - Multi-agent orchestration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and aggregates status information about running scenarios and their tasks. It takes an orchestration_id as input and returns JSON status data. The operation has no side effects—it does not create, modify, delete, or execute any tasks or workflows. It is purely a monitoring/observability function that reads existing state.
From the tool's definition Tool name 'bernstein_scenario_status' and description 'Aggregate the status of all tasks of a running scenario' indicates a read-only query operation that retrieves status information without modifying state.
Documented attack patterns abuse exactly the kind of access bernstein_scenario_status 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_scenario_status:
{
"version": "1",
"default": "deny",
"tools": {
"bernstein_scenario_status": {}
}
}bernstein_scenario_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Aggregate the status of all tasks of a running scenario. Args: orchestration_id: Value returned by bernstein_scenario. Returns: JSON with status counts and per-task details. It is categorised as a Read tool in the Bernstein - Multi-agent orchestration MCP Server, which means it retrieves data without modifying state.
Register the Bernstein - Multi-agent orchestration MCP server in PolicyLayer and add a rule for bernstein_scenario_status: 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_scenario_status 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 bernstein_scenario_status 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_scenario_status. 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_scenario_status 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.