zephyr_create_test_cycle_web_link

Create a new Web Link for a Test Cycle in Zephyr Examples: 1. Create a link between the specified test cycle by Id '100001' and generic URL 'https://www.atlassian.com' with description 'Atlassian homepage' json { "testCycleIdOrKey": "100001", "url": "https://www.atlassian.com", "description": "At...

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp
Medium RISK CLASS
Category Write
Parameters 31 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/zephyr-create-test-cycle-web-link.md

What zephyr_create_test_cycle_web_link does on SmartBear MCP

AI agents use zephyr_create_test_cycle_web_link to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.

ParameterTypeRequiredDescription
url string The web link URL
description string The web link description
testCycleIdOrKey string Yes The ID or key of the test cycle.

Parameters from the server's own tool schema.

Why zephyr_create_test_cycle_web_link is rated Medium

This tool creates new data (web links) in a test management system, which is a reversible write operation. The blast radius is medium because malicious actors could create misleading or fraudulent links associated with test cycles, potentially misdirecting teams or injecting malicious URLs into test documentation, but this does not involve deletion, code execution, or financial impact.

From the tool's definition Tool name indicates 'create' action; description states 'Create a new Web Link for a Test Cycle'; examples show creating new resources with testCycleIdOrKey, url, and description parameters that result in 'newly created Web Link with its ID'.

Risk signalsAccepts URL/endpoint input (url)

Questions about zephyr_create_test_cycle_web_link

What does the zephyr_create_test_cycle_web_link tool do? +

Create a new Web Link for a Test Cycle in Zephyr Examples: 1. Create a link between the specified test cycle by Id '100001' and generic URL 'https://www.atlassian.com' with description 'Atlassian homepage' json { "testCycleIdOrKey": "100001", "url": "https://www.atlassian.com", "description": "Atlassian homepage" } Expected Output: The newly created Web Link with its ID and self link 2. Create a web link for test cycle 'SA-R15' pointing to url: 'https://atlassian.com' with description 'Atlassian homepage' json { "testCycleIdOrKey": "SA-R15", "url": "https://atlassian.com", "description": "Documentation for pump specifications" } Expected Output: The newly created Web Link with its ID and self link 3. Attach a documentation link 'https://docs.atlassian.com' to test cycle MM2-R15 for pump specifications json { "testCycleIdOrKey": "10001", "url": "https://docs.atlassian.com", "description": "Documentation for pump specifications" } Expected Output: The newly created Web Link with its ID and self link. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does zephyr_create_test_cycle_web_link accept? +

zephyr_create_test_cycle_web_link accepts 3 parameters: url, description, testCycleIdOrKey. Required: testCycleIdOrKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on zephyr_create_test_cycle_web_link? +

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

zephyr_create_test_cycle_web_link is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit zephyr_create_test_cycle_web_link? +

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

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

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