遍歷 test-results/history/*.json 快照（每次 run_tests 完會自動歸檔），
AI agents call get_test_history to retrieve information from Mk Qa Master without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries historical test result data without modifying, deleting, or executing anything. It has no side effects beyond data retrieval. The low severity reflects that accessing test history poses minimal risk—it cannot alter test runs, delete data, or trigger external operations.
From the tool's definition Tool traverses and reads test-results/history/*.json snapshots that are automatically archived after each run_tests execution. The description uses '遍歷' (traverse/iterate) and indicates reading archived JSON files.
Documented attack patterns abuse exactly the kind of access get_test_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mk Qa Master, and nothing reaches the server without passing your rules. This is the rule we recommend for get_test_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_test_history": {}
}
}get_test_history 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.
遍歷 test-results/history/*.json 快照（每次 run_tests 完會自動歸檔），. It is categorised as a Read tool in the Mk Qa Master MCP Server, which means it retrieves data without modifying state.
Register the Mk Qa Master 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 Mk Qa Master. Nothing to install.
get_test_history 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 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.
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.
get_test_history is provided by the Mk Qa Master MCP server (kao273183/mk-qa-master). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mk Qa Master, 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.
22 Mk Qa Master tools catalogued and risk-classified — across an index of 43,000+ MCP servers.