Create a new Test Case in Zephyr specified project **Parameters:** - projectKey (string) *required*: Jira project key. - name (string) *required* - objective (string): A description of the objective. - precondition (string): Any conditions that need to be met. - estimatedTime (number): Estimated...
High parameter count (12 properties)
Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use zephyr_create_test_case to create or modify resources in SmartBear MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call zephyr_create_test_case repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SmartBear MCP.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
zephyr_create_test_case:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full SmartBear MCP policy for all 243 tools.
Agents calling write-class tools like zephyr_create_test_case have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Create a new Test Case in Zephyr specified project **Parameters:** - projectKey (string) *required*: Jira project key. - name (string) *required* - objective (string): A description of the objective. - precondition (string): Any conditions that need to be met. - estimatedTime (number): Estimated duration in milliseconds. - componentId (number): ID of a component from Jira. - priorityName (string): The priority name. - statusName (string): The status name. - folderId (number): ID of a folder to place the entity within. - ownerId (string): Atlassian Account ID of the Jira user. - labels (array): Array of labels associated to this entity. - customFields (record<string, any>): Multi-line text fields support HTML and should denote new lines with the \<br\> tag. Dates should be in the format 'yyyy-MM-dd'. Users should have values of Jira User Account IDs. **Examples:** 1. Create a Test Case in project SA to ensure that the axial pump can be enabled ```json { "projectKey": "SA", "name": "Check axial pump", "objective": "Ensure the axial pump can be enabled" } ``` Expected Output: The newly created Test Case with its details and key 2. Create a Test Case to ensure that the axial pump can be enabled. The test should be in project MM2, have labels 'automated' and 'mcp', and priority 'High' ```json { "projectKey": "MM2", "name": "Check axial pump", "objective": "Ensure the axial pump can be enabled", "labels": [ "automated", "mcp" ], "priorityName": "High" } ``` Expected Output: The newly created Test Case with its details and key 3. Create a Test Case for verifying strength of the axial pump with custom field 'Axial pump strength' having value '5' in project SA ```json { "projectKey": "SA", "name": "Check axial pump strength", "objective": "Make sure the axial pump operates at the required strength", "customFields": { "Axial pump strength": 5 } } ``` Expected Output: The newly created Test Case with its details and key 4. Create a Test Case in project MM2 to verify the performance of the axial pump with Jira component having ID 10001, Jira owner having ID 10057 in folder 'Pumps' ```json { "projectKey": "MM2", "name": "Check axial pump performance", "objective": "Ensure the axial pump performs within acceptable limits", "componentId": 10001, "ownerJiraUserId": 10057, "folderId": 18 } ``` Expected Output: The newly created Test Case with its details and key. 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.
Add a rule in your Intercept YAML policy under the tools section for zephyr_create_test_case. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.
zephyr_create_test_case is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zephyr_create_test_case rule in your Intercept 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 Intercept policy for zephyr_create_test_case. 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_create_test_case is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.