Create PLAN_PROJECT_ROOT/plan-knowledge.md from a starter
AI agents use init_plan_knowledge to create or update resources in Mk Plan Master — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mk Plan Master environment.
This tool creates a new markdown file in a project directory. File creation is a Write operation (reversible via deletion). The severity is medium because creating files can affect project state and downstream processes, but the action is not destructive (file can be deleted) nor does it execute arbitrary code or move money. Confidence is high due to explicit 'Create' language in the description.
From the tool's definition Tool description states 'Create PLAN_PROJECT_ROOT/plan-knowledge.md from a starter' — the verb 'Create' indicates file creation, a reversible write operation.
Attacks that exploit this kind of access
Create PLAN_PROJECT_ROOT/plan-knowledge.md from a starter. It is categorised as a Write tool in the Mk Plan Master MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mk Plan Master MCP server in PolicyLayer and add a rule for init_plan_knowledge: 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.
init_plan_knowledge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the init_plan_knowledge 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 init_plan_knowledge. 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.
init_plan_knowledge 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 →