zephyr_get_test_execution_links

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

WHAT IT DOES

What zephyr_get_test_execution_links does on SmartBear MCP

AI agents call zephyr_get_test_execution_links 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
`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.

RISK

Why zephyr_get_test_execution_links is rated Low

This tool retrieves and returns information about test execution links without modifying any data or triggering side effects. It is a straightforward read/query operation on test management data. The blast radius of misuse is minimal - an agent could only access test execution metadata that may already be available through other means.

From the tool's definition Tool name and description explicitly indicate 'Get links for a specific test execution' - a retrieval operation that queries test execution data and returns link details. The parameter accepts an ID or key to identify which execution to retrieve.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zephyr_get_test_execution_links 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_execution_links, this is the rule to start with:

zephyr_get_test_execution_links Allowed

zephyr_get_test_execution_links is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zephyr_get_test_execution_links": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_get_test_execution_links call is checked against it from then on.

FAQ

Questions about zephyr_get_test_execution_links

What does the zephyr_get_test_execution_links tool do? +

Get links for a specific test execution 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 links oftest execution with id 1 json { "testExecutionIdOrKey": "1" } Expected Output: The test execution links with its details 2. Get the links of test execution with key 'PROJ-E123' json { "testExecutionIdOrKey": "PROJ-E123" } Expected Output: The test execution links 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_links accept? +

zephyr_get_test_execution_links 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_links? +

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

zephyr_get_test_execution_links 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_links? +

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

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

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

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →