get_test_history

Get test history summary with aggregated statistics including pass rate, total runs, and recent results.

Server Qontinui MCP Server qontinui/qontinui-mcp
Category Read
Risk class Low
Parameters 00 required

What get_test_history does on Qontinui MCP Server

AI agents call get_test_history to retrieve information from Qontinui MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_test_history needs a policy

This tool retrieves and queries historical test data and aggregated statistics. It performs no modifications, deletions, executions, or financial operations. The operation is purely informational and has no side effects on the system or data beyond standard read access patterns. This is consistent with the Read category definition of 'retrieves or queries data; no side effects.'

From the tool's definition Tool description states it 'Get test history summary with aggregated statistics including pass rate, total runs, and recent results.' The verbs 'Get' and the nature of retrieving historical summaries and statistics indicate a read-only operation with no side…

Questions about get_test_history

What does the get_test_history tool do? +

Get test history summary with aggregated statistics including pass rate, total runs, and recent results. It is categorised as a Read tool in the Qontinui MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_test_history? +

Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for get_test_history: 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 Qontinui MCP Server. Nothing to install.

What risk level is get_test_history? +

get_test_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_test_history? +

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

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

get_test_history is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.