Get the full operation history of the document
AI agents call get_history to retrieve information from AI-Canvas MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical metadata about operations performed on a design document. It does not modify, delete, or execute any operations—it merely retrieves and presents existing log data. This is a classic Read operation with minimal risk; the primary concern would be information disclosure if sensitive design decisions or user actions were exposed, but the blast radius remains low.
From the tool's definition Tool name 'get_history' with description 'Get the full operation history of the document' indicates a retrieval operation with no side effects. The verb 'Get' and the read-only nature of querying historical records confirm this is a data retrieval action.
Attacks that exploit this kind of access
Get the full operation history of the document. It is categorised as a Read tool in the AI-Canvas MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AI-Canvas MCP Server MCP server in PolicyLayer and add a rule for get_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 AI-Canvas MCP Server. Nothing to install.
get_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_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_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_history is provided by the AI-Canvas MCP Server MCP server (laoluojuhai/ai-canvas). 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 →