alm_create_requirement · HP ALM MCP Server MCP

WHAT IT DOES

What alm_create_requirement does on HP ALM MCP Server

AI agents use alm_create_requirement 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.

WHY IT NEEDS A POLICY

Why alm_create_requirement needs a policy

Requirements creation is a reversible write operation that modifies QA management data. It does not execute external code, delete data permanently, or move financial resources. While the description is empty, the tool name combined with the server context (QA workflows) and sibling tools clearly indicate this creates new requirement records, fitting the Write category.

From the tool's definition Tool name 'alm_create_requirement' indicates creation of requirements in HP ALM/Quality Center. Sibling tools like 'alm_create_defect', 'alm_create_test_case', and 'alm_create_test_run' all perform reversible write operations within QA workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

alm_create_requirement Rate-limited

alm_create_requirement 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "alm_create_requirement": {
      "limits": [
        {
          "counter": "alm_create_requirement_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HP ALM MCP Server, so you can run agents against it safely.

FAQ

Questions about alm_create_requirement

What does the alm_create_requirement tool do? +

alm_create_requirement. 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.

How do I enforce a policy on alm_create_requirement? +

Register the HP ALM MCP Server MCP server in PolicyLayer and add a rule for alm_create_requirement: 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.

What risk level is alm_create_requirement? +

alm_create_requirement is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit alm_create_requirement? +

Yes. Add a rate_limit block to the alm_create_requirement 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.

How do I block alm_create_requirement completely? +

Set action: deny in the PolicyLayer policy for alm_create_requirement. 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.

What MCP server provides alm_create_requirement? +

alm_create_requirement 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.