alm_add_design_steps
AI agents use alm_add_design_steps 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.
The tool performs a write operation on test design data. While the description is empty (reducing confidence), the name and context strongly suggest it modifies test case design steps—a reversible change consistent with Write category. Severity is medium because misuse could corrupt test designs affecting QA processes, but changes are typically reviewable and undoable through ALM's version control mechanisms.
From the tool's definition Tool name 'alm_add_design_steps' indicates modification of test design artifacts within HP ALM. The 'add' prefix suggests creating or appending steps to existing test entities (likely test cases).
Attacks that exploit this kind of access
alm_add_design_steps. 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_add_design_steps: 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_add_design_steps 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_add_design_steps 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_add_design_steps. 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_add_design_steps 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 →