Get active test runs from LoadRunner Cloud.
AI agents call test_runs_getActiveTestRuns to retrieve information from LoadRunner Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about active test runs without modifying, executing, or deleting any data. It is a straightforward query operation that returns performance test status and metadata. No side effects, no code execution, no financial impact, and no irreversible changes are possible.
From the tool's definition Tool name 'test_runs_getActiveTestRuns' with verb 'get' and description 'Get active test runs from LoadRunner Cloud' indicates data retrieval operation.
Attacks that exploit this kind of access
Get active test runs from LoadRunner Cloud. It is categorised as a Read tool in the LoadRunner Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LoadRunner Cloud MCP Server MCP server in PolicyLayer and add a rule for test_runs_getActiveTestRuns: 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 LoadRunner Cloud MCP Server. Nothing to install.
test_runs_getActiveTestRuns 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 test_runs_getActiveTestRuns 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 test_runs_getActiveTestRuns. 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.
test_runs_getActiveTestRuns is provided by the LoadRunner Cloud MCP Server MCP server (pbandreddy/loadrunner-cloud-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 →