alm_execute_test · HP ALM MCP Server MCP: Risk & Policy

WHAT IT DOES

What alm_execute_test does on HP ALM MCP Server

AI agents invoke alm_execute_test to trigger actions in HP ALM MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why alm_execute_test needs a policy

Although the description is empty, the tool name combined with the server's stated purpose (test execution within HP ALM) clearly indicates this tool runs/executes test cases. Execution of tests in a QA system can have side effects including state changes in the ALM system, triggering external integrations, and affecting test results and metrics.

From the tool's definition Tool name 'alm_execute_test' indicates execution of test cases in HP ALM/Quality Center. In the context of QA workflow management, executing tests constitutes running code or triggering external operations with effects dependent on test parameters and system…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

alm_execute_test Rate-limited

alm_execute_test stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_execute_test": {
      "limits": [
        {
          "counter": "alm_execute_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_execute_test

What does the alm_execute_test tool do? +

alm_execute_test. It is categorised as a Execute tool in the HP ALM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on alm_execute_test? +

Register the HP ALM MCP Server MCP server in PolicyLayer and add a rule for alm_execute_test: 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_execute_test? +

alm_execute_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit alm_execute_test? +

Yes. Add a rate_limit block to the alm_execute_test 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_execute_test completely? +

Set action: deny in the PolicyLayer policy for alm_execute_test. 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_execute_test? +

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