Return trend deltas (current vs ~7 days ago / vs window_days ago)
AI agents call get_planning_history 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 and returns historical trend data for analysis purposes. It performs a read-only query operation with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an agent could only view historical planning information, not change it or trigger external operations.
From the tool's definition Tool name 'get_planning_history' and description 'Return trend deltas (current vs ~7 days ago / vs window_days ago)' indicate a retrieval operation that queries historical planning data and computes comparative metrics without modifying, executing, or…
Attacks that exploit this kind of access
Return trend deltas (current vs ~7 days ago / vs window_days ago). 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_planning_history: 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_planning_history 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_planning_history 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_planning_history. 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_planning_history 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 →