AI agents call track_changes to retrieve information from Claude Writer's Aid MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays changes made to a document since a specified point in time. It has no side effects—it only queries and returns historical data without creating, modifying, deleting, or executing anything. This is a classic Read operation, analogous to version control diff commands used for inspection purposes.
From the tool's definition Tool description 'Show what changed since timestamp' indicates retrieval of historical change data. The sibling tools on this server (analyze_link_graph, check_readability, check_terminology, extract_themes, find_broken_links, etc.) are all Read operations…
Documented attack patterns abuse exactly the kind of access track_changes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Writer's Aid MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for track_changes:
{
"version": "1",
"default": "deny",
"tools": {
"track_changes": {}
}
}track_changes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show what changed since timestamp. It is categorised as a Read tool in the Claude Writer's Aid MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Writer's Aid MCP server in PolicyLayer and add a rule for track_changes: 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 Claude Writer's Aid MCP. Nothing to install.
track_changes 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 track_changes 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 track_changes. 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.
track_changes is provided by the Claude Writer's Aid MCP server (xiaolai/claude-writers-aid-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Writer's Aid MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Claude Writer's Aid MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.