AI agents call testcase_get_step 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 or queries test case step/scenario data without modifying, creating, or deleting anything. It is a straightforward data retrieval operation consistent with the Read category. Severity is low as it only exposes test metadata with no blast radius for misuse.
From the tool's definition Tool name 'testcase_get_step' and alias 'testcase_get_scenario' indicate retrieval of test case steps/scenarios. The 'get' verb and read-only semantics (retrieving test case data) classify this as a Read operation with no side effects.
Attacks that exploit this kind of access
Alias for testcase_get_scenario. 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_step: 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_step 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_step 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_step. 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_step 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 →