zephyr_get_test_script
Get the Test Script (Plain Text or BDD) for a given Test Case in Zephyr Parameters: - testCaseKey (string) *required*: The key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+ Examples: 1. Get the test script for test case with key 'SA-T1' json { "testCaseKey": "SA-T1" } Expected...
This record as markdown: /tools/smartbear-mcp/zephyr-get-test-script.md
What zephyr_get_test_script does on SmartBear MCP
AI agents call zephyr_get_test_script to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
testCaseKey | string | Yes | The key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+ |
Parameters from the server's own tool schema.
Why zephyr_get_test_script is rated Low
This tool retrieves and queries test script data from Zephyr without any side effects. It performs a read-only operation to fetch existing test case information, which aligns with the Read category (search, list, get, fetch). No data is created, modified, deleted, or executed.
From the tool's definition Tool description states 'Get the Test Script' and examples show retrieval of test script content with no modification, deletion, or execution capabilities. The tool accepts a testCaseKey parameter and returns test script data.
Attacks that exploit this kind of access
The rule that runs zephyr_get_test_script safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zephyr_get_test_script, this is the rule to start with:
zephyr_get_test_script is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_get_test_script call is checked against it from then on.
Questions about zephyr_get_test_script
Get the Test Script (Plain Text or BDD) for a given Test Case in Zephyr Parameters: - testCaseKey (string) *required*: The key of the test case. Test case keys are of the format [A-Z]+-T[0-9]+ Examples: 1. Get the test script for test case with key 'SA-T1' json { "testCaseKey": "SA-T1" } Expected Output: The test script with its type (plain or bdd), text content, and id 2. Retrieve the BDD test script content for test case with key 'MM2-T15' json { "testCaseKey": "MM2-T15" } Expected Output: The test script with its type (plain or bdd), text content, and id 3. Get the test script for test case with key 'QA-T100' to review the test instructions json { "testCaseKey": "QA-T100" } Expected Output: The test script with its type (plain or bdd), text content, and id. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
zephyr_get_test_script accepts 1 parameter: testCaseKey. Required: testCaseKey. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_get_test_script: 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 SmartBear MCP. Nothing to install.
zephyr_get_test_script 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 zephyr_get_test_script 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 zephyr_get_test_script. 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.
zephyr_get_test_script is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue