AI agents call testcase_get_scenario to retrieve information from Testops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns test scenario metadata in JSON format. The verb 'get' and the descriptive focus on returning structured data (scenarioSteps, step bodies, expected results) clearly indicate a read-only operation. There are no side effects, no code execution, no data modification, and no destructive actions.
From the tool's definition Tool name 'testcase_get_scenario' and description indicate retrieval of normalized scenario JSON data (scenarioSteps, step bodies, expected results) — a pure data query operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Normalized scenario JSON (scenarioSteps, step bodies, expected results). It is categorised as a Read tool in the Testops MCP Server, which means it retrieves data without modifying state.
Register the Testops MCP server in PolicyLayer and add a rule for testcase_get_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 Testops. Nothing to install.
testcase_get_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 testcase_get_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 testcase_get_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.
testcase_get_scenario is provided by the Testops MCP server (@syn7xx/testops-mcp-server). 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 →