Get folders from Zephyr Scale. All parameters are optional. If folder_path is provided, returns the full subtree (the folder and all its descendants at every depth) under that path. Otherwise returns all folders matching the filters.
AI agents call get_folders to retrieve information from Zephyr Scale MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that retrieves folder information from the test management system. The parameters are optional filters for retrieval, and the response is informational data about folder structure. There are no mutations, deletions, or external operations triggered. The blast radius is minimal as misuse would only expose information the requester already has access to in Jira Cloud/Data Center.
From the tool's definition Tool name is 'get_folders' and description states it 'returns' folders matching filters or a folder subtree. The action is purely retrieval with 'no side effects' — it queries and fetches data without modifying or deleting anything.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get folders from Zephyr Scale. All parameters are optional. If folder_path is provided, returns the full subtree (the folder and all its descendants at every depth) under that path. Otherwise returns all folders matching the filters. It is categorised as a Read tool in the Zephyr Scale MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for get_folders: 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 Zephyr Scale MCP Server. Nothing to install.
get_folders is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_folders 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 get_folders. 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.
get_folders is provided by the Zephyr Scale MCP Server MCP server (milo0821/zephyr_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →