the getTestReport tool can retrieve a test report for a given test target and test report id. A test report id is generated when a set of test are executed on a test target. The test report id is unique to the test target.
AI agents call getTestReport to retrieve information from Octomind without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and returns existing test report data based on identifiers (test target and test report id). There is no modification, deletion, execution, or financial impact. This is a straightforward data retrieval operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'getTestReport' and description state it 'can retrieve a test report' — a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access getTestReport gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octomind, and nothing reaches the server without passing your rules. This is the rule we recommend for getTestReport:
{
"version": "1",
"default": "deny",
"tools": {
"getTestReport": {}
}
}getTestReport is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
the getTestReport tool can retrieve a test report for a given test target and test report id. A test report id is generated when a set of test are executed on a test target. The test report id is unique to the test target. It is categorised as a Read tool in the Octomind MCP Server, which means it retrieves data without modifying state.
Register the Octomind MCP server in PolicyLayer and add a rule for getTestReport: 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 Octomind. Nothing to install.
getTestReport 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 getTestReport 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 getTestReport. 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.
getTestReport is provided by the Octomind MCP server (octomind-dev/octomind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Octomind, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Octomind tools catalogued and risk-classified — across an index of 43,000+ MCP servers.