Three-layer coach output that integrates coverage /
AI agents call get_optimization_plan to retrieve information from Mk Spec Master without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or generate analysis/recommendations about optimization strategy by examining coverage metrics and other spec data. It does not create persistent resources, execute external commands, delete data, or move money. Aligned with sibling tools like 'analyze_spec_quality' and 'get_coverage_matrix', which are read operations.
From the tool's definition Tool name 'get_optimization_plan' and description fragment 'Three-layer coach output that integrates coverage' indicate a retrieval/analysis operation that produces coaching recommendations based on existing spec and coverage data.
Attacks that exploit this kind of access
Three-layer coach output that integrates coverage /. It is categorised as a Read tool in the Mk Spec Master MCP Server, which means it retrieves data without modifying state.
Register the Mk Spec 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 Spec 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 Spec Master MCP server (kao273183/mk-spec-master). 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 →