AI agents call testplan_get_stat to retrieve information from Testops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns statistical information about test plans (counts, durations) without creating, modifying, deleting, or executing operations. It is purely informational and has no side effects, fitting the Read category. The low severity reflects minimal blast radius if misused by an AI agent—it can only expose existing test metadata.
From the tool's definition Tool retrieves 'Test plan statistics: automated/manual counts, durations' with no modification capability. The verb 'get' and description 'Useful before running to estimate effort' indicate data retrieval only.
Attacks that exploit this kind of access
Test plan statistics: automated/manual counts, durations. Useful before running to estimate effort. It is categorised as a Read tool in the Testops MCP Server, which means it retrieves data without modifying state.
Register the Testops MCP server in PolicyLayer and add a rule for testplan_get_stat: 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 Testops. Nothing to install.
testplan_get_stat 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 testplan_get_stat 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 testplan_get_stat. 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.
testplan_get_stat is provided by the Testops MCP server (@syn7xx/testops-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 →