📜 Get change request history for workflow: all past changes, approvals, rejections with timestamps.
AI agents call get_change_history to retrieve information from n8n Workflow Builder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries audit/change history records without creating, modifying, deleting, or executing actions. It is a straightforward retrieval operation with no side effects, fitting the Read category. Severity is low because exposing historical metadata poses minimal risk even if queried inappropriately—the data is already in the system and no new changes are triggered.
From the tool's definition Tool retrieves historical data ('all past changes, approvals, rejections with timestamps') with no mutation operations described. The verb 'Get' and the emoji '📜' (document/history) indicate query-only semantics.
Attacks that exploit this kind of access
📜 Get change request history for workflow: all past changes, approvals, rejections with timestamps. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for get_change_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 n8n Workflow Builder. Nothing to install.
get_change_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_change_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_change_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_change_history is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). 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 →