Get a runtime-aware scenario projection - like project_scenarios, but
AI agents call project_current_scenario to retrieve information from Qontinui MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries runtime scenario information without modifying state. However, in the context of a visual automation and workflow execution system, accessing 'runtime-aware' projections could inform downstream Execute or Destructive actions, warranting medium severity. The incomplete description ('like project_scenarios, but') reduces confidence slightly.
From the tool's definition Tool name 'project_current_scenario' and description fragment 'Get a runtime-aware scenario projection' indicate data retrieval. No description of modification, deletion, or command execution is stated.
Attacks that exploit this kind of access
Get a runtime-aware scenario projection - like project_scenarios, but. It is categorised as a Read tool in the Qontinui MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for project_current_scenario: 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 Qontinui MCP Server. Nothing to install.
project_current_scenario 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 project_current_scenario 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 project_current_scenario. 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.
project_current_scenario is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-mcp). 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 →