List the scenario ids this server can diagnose, with a short description each.
AI agents call list_known_scenarios to retrieve information from SchedulerRX · Constraint Debugger Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation. It queries existing scenarios and returns information about them. There is no creation, modification, deletion, code execution, or financial impact. The tool has minimal blast radius even if invoked by an AI agent, as it merely returns informational metadata.
From the tool's definition The tool name 'list_known_scenarios' and description 'List the scenario ids this server can diagnose, with a short description each' indicate a read-only operation that retrieves and enumerates data without modification, side effects, or external execution.
Attacks that exploit this kind of access
List the scenario ids this server can diagnose, with a short description each. It is categorised as a Read tool in the SchedulerRX · Constraint Debugger Agent MCP Server, which means it retrieves data without modifying state.
Register the SchedulerRX · Constraint Debugger Agent MCP server in PolicyLayer and add a rule for list_known_scenarios: 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 SchedulerRX · Constraint Debugger Agent. Nothing to install.
list_known_scenarios 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 list_known_scenarios 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 list_known_scenarios. 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.
list_known_scenarios is provided by the SchedulerRX · Constraint Debugger Agent MCP server (tpinzzz/schedulerrx-constraint-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →