zephyr_get_test_execution

Get details of test execution specified by id or key in Zephyr Parameters: - testExecutionIdOrKey (string) *required*: The ID or key of the test execution. Test execution keys are of the format [A-Z]+-E[0-9]+ Examples: 1. Get the test execution with id 1 json { "testExecutionIdOrKey": "1" } Expec...

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

What zephyr_get_test_execution does on SmartBear MCP

AI agents call zephyr_get_test_execution 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
testExecutionIdOrKey string Yes The ID or key of the test execution. Test execution keys are of the format [A-Z]+-E[0-9]+

Parameters from the server's own tool schema.

Why zephyr_get_test_execution is rated Low

This tool retrieves and queries test execution details from Zephyr without any side effects, creation, modification, or deletion. It is a straightforward data retrieval operation. Severity is low as misuse would only expose test execution metadata without enabling harmful changes to systems or data.

From the tool's definition Tool name is 'zephyr_get_test_execution' with description 'Get details of test execution specified by id or key in Zephyr'. The verb 'Get' and the parameter 'testExecutionIdOrKey' indicate retrieval of existing data without modification.

Questions about zephyr_get_test_execution

What does the zephyr_get_test_execution tool do? +

Get details of test execution specified by id or key in Zephyr Parameters: - testExecutionIdOrKey (string) *required*: The ID or key of the test execution. Test execution keys are of the format [A-Z]+-E[0-9]+ Examples: 1. Get the test execution with id 1 json { "testExecutionIdOrKey": "1" } Expected Output: The test execution with its details 2. Get the test execution with key 'PROJ-E123' json { "testExecutionIdOrKey": "PROJ-E123" } Expected Output: The test execution with its details. 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_execution accept? +

zephyr_get_test_execution accepts 1 parameter: testExecutionIdOrKey. Required: testExecutionIdOrKey. 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_execution? +

Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_get_test_execution: 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_execution? +

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

Can I rate-limit zephyr_get_test_execution? +

Yes. Add a rate_limit block to the zephyr_get_test_execution 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_execution completely? +

Set action: deny in the PolicyLayer policy for zephyr_get_test_execution. 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_execution? +

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