Retrieve load tests for a project.
AI agents call projects_getLoadTests 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 fetches performance test metadata and results from LoadRunner Cloud. It has no capability to delete, modify, execute code, or trigger financial transactions. The blast radius of misuse is minimal—an AI agent could retrieve test data it shouldn't see, but cannot alter systems or cause operational harm. Classification as Read with low severity is appropriate.
From the tool's definition Tool name 'projects_getLoadTests' and description 'Retrieve load tests for a project' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieve load tests for a project. 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 projects_getLoadTests: 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.
projects_getLoadTests 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 projects_getLoadTests 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 projects_getLoadTests. 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.
projects_getLoadTests 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 →