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 (...
Admin/system-level operation
Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use zephyr_create_folder 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_folder 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_folder:
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_folder 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 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.
Add a rule in your Intercept YAML policy under the tools section for zephyr_create_folder. 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_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 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_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 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.