Pull a single initiative by id from the active source. Returns
AI agents call fetch_initiative 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 initiative data from a source without modifying, deleting, or executing external operations. The operation is a straightforward data query by identifier. Low severity because unauthorized access returns only planning/roadmap data without financial, system execution, or destructive consequences. High confidence due to clear descriptive language indicating a simple retrieval operation.
From the tool's definition Tool name 'fetch_initiative' and description 'Pull a single initiative by id from the active source' indicate retrieval of data by identifier.
Attacks that exploit this kind of access
Pull a single initiative by id from the active source. Returns. 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 fetch_initiative: 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.
fetch_initiative 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 fetch_initiative 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 fetch_initiative. 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.
fetch_initiative 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 →