Get version history of a guideline including current version and all previous versions with timestamps
AI agents call get_guideline_history to retrieve information from Planning Game without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries version history data with no side effects. It follows the Read category pattern of fetching/getting information (get_) without creating, modifying, deleting, or executing external operations. The data retrieved is historical metadata about guidelines, making it a low-severity read operation.
From the tool's definition Tool name 'get_guideline_history' and description 'Get version history of a guideline including current version and all previous versions with timestamps' indicates a retrieval operation that queries historical data without modification.
Attacks that exploit this kind of access
Get version history of a guideline including current version and all previous versions with timestamps. It is categorised as a Read tool in the Planning Game MCP Server, which means it retrieves data without modifying state.
Register the Planning Game MCP server in PolicyLayer and add a rule for get_guideline_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 Planning Game. Nothing to install.
get_guideline_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_guideline_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_guideline_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_guideline_history is provided by the Planning Game MCP server (planning-game-mcp). 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 →