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...

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about zephyr_get_test_script

What does the zephyr_get_test_script tool do? +

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.

What parameters does zephyr_get_test_script accept? +

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.

How do I enforce a policy on zephyr_get_test_script? +

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.

What risk level is zephyr_get_test_script? +

zephyr_get_test_script is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zephyr_get_test_script? +

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.

How do I block zephyr_get_test_script completely? +

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.

What MCP server provides zephyr_get_test_script? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of SmartBear's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.