Create test steps for a test case.
AI agents use create_test_case_steps to create or update resources in Zephyr Scale MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zephyr Scale MCP Server environment.
This tool creates new test case steps within a test management system. It is reversible (steps can be modified or deleted later) and has no irreversible destructive effects, financial impact, or code execution capabilities. The blast radius is limited to test case metadata in a quality assurance workflow.
From the tool's definition Tool name is 'create_test_case_steps' and description states 'Create test steps for a test case.' The verb 'create' indicates data creation rather than retrieval or deletion.
Attacks that exploit this kind of access
Create test steps for a test case. It is categorised as a Write tool in the Zephyr Scale MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for create_test_case_steps: 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 Zephyr Scale MCP Server. Nothing to install.
create_test_case_steps is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_test_case_steps 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 create_test_case_steps. 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.
create_test_case_steps is provided by the Zephyr Scale MCP Server MCP server (metquay/zephyr-scale-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 →