綜合 history/ 快照、telemetry tool-usage、analyze_url 偵測過的 modules，
AI agents call get_optimization_plan 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 aggregates and queries existing QA telemetry and analysis data to generate optimization recommendations. While it reads potentially sensitive test performance and usage data (medium severity for information disclosure risk), it performs no write, execute, destructive, or financial operations. The blast radius is limited to data exposure rather than system compromise or irreversible actions.
From the tool's definition Tool name 'get_optimization_plan' and description indicate it retrieves and synthesizes historical data, snapshots, telemetry, and analysis results ("綜合 history/ 快照、telemetry tool-usage、analyze_url 偵測過的 modules").
Documented attack patterns abuse exactly the kind of access get_optimization_plan 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_optimization_plan:
{
"version": "1",
"default": "deny",
"tools": {
"get_optimization_plan": {}
}
}get_optimization_plan 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.
綜合 history/ 快照、telemetry tool-usage、analyze_url 偵測過的 modules，. 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_optimization_plan: 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_optimization_plan 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_optimization_plan 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_optimization_plan. 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_optimization_plan 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.