Read PLAN_PROJECT_ROOT/plan-knowledge.md (or fall back to built-in
AI agents call get_plan_context to retrieve information from Mk Plan Master without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves planning context documentation from a local markdown file or built-in defaults. It has no capability to modify data, execute code, delete resources, or commit financial transactions. The read-only nature and bounded scope (single file access) place it firmly in the Read category with low severity—misuse would only expose planning information, not cause operational harm.
From the tool's definition Tool description explicitly states 'Read PLAN_PROJECT_ROOT/plan-knowledge.md' and fallback behavior; the verb 'Read' and 'get_' prefix indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Read PLAN_PROJECT_ROOT/plan-knowledge.md (or fall back to built-in. It is categorised as a Read tool in the Mk Plan Master MCP Server, which means it retrieves data without modifying state.
Register the Mk Plan Master MCP server in PolicyLayer and add a rule for get_plan_context: 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 Plan Master. Nothing to install.
get_plan_context 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_plan_context 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_plan_context. 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_plan_context is provided by the Mk Plan Master MCP server (kao273183/mk-plan-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 →