Ensure a Test Lab (test-set) folder path exists, creating any missing folders.
AI agents use alm_ensure_test_lab_folder to create or update resources in HP ALM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HP ALM MCP Server environment.
This tool creates folder structures in HP ALM's Test Lab if they don't already exist. It writes/creates new folder entities but does not delete or overwrite anything, making it a Write operation. The blast radius is low since creating empty folders has minimal adverse impact.
From the tool's definition Ensure a Test Lab (test-set) folder path exists, creating any missing folders.
Attacks that exploit this kind of access
Ensure a Test Lab (test-set) folder path exists, creating any missing folders. It is categorised as a Write tool in the HP ALM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HP ALM MCP Server MCP server in PolicyLayer and add a rule for alm_ensure_test_lab_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 HP ALM MCP Server. Nothing to install.
alm_ensure_test_lab_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 alm_ensure_test_lab_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 alm_ensure_test_lab_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.
alm_ensure_test_lab_folder is provided by the HP ALM MCP Server MCP server (uditmahaldar/opentext-alm-mcp). 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 →