zephyr_create_folder
Create a folder called 'Axial Pump Tests' in the project SA for organizing test cases Parameters: - parentId (number): Folder ID of the parent folder. Must be null for root folders. - name (string) *required*: Folder name. Folder name must not contain / and \ characters. - projectKey (string) *re...
This record as markdown: /tools/smartbear-mcp/zephyr-create-folder.md
What zephyr_create_folder does on SmartBear MCP
AI agents use zephyr_create_folder 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Folder name. Folder name must not contain `/` and `\` characters. |
parentId | number | — | Folder ID of the parent folder. Must be `null` for root folders. |
folderType | string | Yes | Valid values: `"TEST_CASE"`, `"TEST_PLAN"`, `"TEST_CYCLE"` |
projectKey | string | Yes | Jira project key. |
Parameters from the server's own tool schema.
Why zephyr_create_folder is rated Medium
This tool creates a new folder for organizing test cases in a Jira project, which is a reversible write operation. It does not execute code, delete data, move money, or retrieve sensitive information.
From the tool's definition Tool name 'zephyr_create_folder' and description 'Create a folder' indicate creation of a new organizational structure. Parameters include 'name', 'projectKey', and 'folderType' which are used to create a folder resource.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs zephyr_create_folder 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_create_folder, this is the rule to start with:
zephyr_create_folder stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every zephyr_create_folder call is checked against it from then on.
Questions about zephyr_create_folder
Create a folder called 'Axial Pump Tests' in the project SA for organizing test cases Parameters: - parentId (number): Folder ID of the parent folder. Must be null for root folders. - name (string) *required*: Folder name. Folder name must not contain / and \ characters. - projectKey (string) *required*: Jira project key. - folderType (string) *required*: Valid values: "TEST_CASE", "TEST_PLAN", "TEST_CYCLE" Examples: 1. Create a root Folder in project SA for organizing test cases json { "parentId": null, "name": "Axial Pump Tests", "projectKey": "SA", "folderType": "TEST_CASE" } Expected Output: The newly created Folder with its ID and self link 2. Create a sub-folder under folder ID 5 in the project MM2 for test plans related to pumps json { "parentId": 5, "name": "Pump-related Test Plans", "projectKey": "MM2", "folderType": "TEST_PLAN" } Expected Output: The newly created Folder with its ID and self link 3. Create a Folder called 'Regression Cycles' in project TIS for organizing test cycles json { "parentId": null, "name": "Regression Cycles", "projectKey": "TIS", "folderType": "TEST_CYCLE" } Expected Output: The newly created Folder 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.
zephyr_create_folder accepts 4 parameters: name, parentId, folderType, projectKey. Required: name, folderType, projectKey. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for zephyr_create_folder: 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.
zephyr_create_folder 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_folder 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.
Set action: deny in the PolicyLayer policy for zephyr_create_folder. 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_folder 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.
This server
Across the catalogue