Return a summary of all task counts from the Bernstein server. Returns: JSON with total, open, claimed, done, failed counts plus a per-role breakdown.
AI agents call bernstein_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 retrieves and queries status information from the Bernstein orchestration server. It has no side effects—it does not create, modify, delete, or execute any operations. The 'Return' verb and the fact that it provides informational summaries (counts and breakdowns) are characteristic of Read operations. Confidence is high because the description is explicit about its read-only nature.
From the tool's definition Tool description states it 'Return[s] a summary' of task counts and provides aggregated metrics and breakdown data with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access bernstein_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_status:
{
"version": "1",
"default": "deny",
"tools": {
"bernstein_status": {}
}
}bernstein_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.
Return a summary of all task counts from the Bernstein server. Returns: JSON with total, open, claimed, done, failed counts plus a per-role breakdown. 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_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_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_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_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_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.