refresh_co_changes
Rebuild co-change index from git history. Mutates the co-change index; idempotent. Use after significant git history changes. Returns JSON: { status, pairs_stored, window_days }.
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/refresh-co-changes.md
What refresh_co_changes does on Trace
AI agents use refresh_co_changes to create or update resources in Trace, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trace environment.
Why refresh_co_changes is rated Medium
The tool mutates (writes to) the co-change index by rebuilding it from git history. It is described as idempotent, meaning it can be re-run without additional side effects beyond the index state, and it does not delete or irreversibly destroy data — it simply overwrites/rebuilds the index. This places it firmly in the Write category.
From the tool's definition Rebuild co-change index from git history. Mutates the co-change index; idempotent.
Attacks that exploit this kind of access
The rule that runs refresh_co_changes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For refresh_co_changes, this is the rule to start with:
refresh_co_changes stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every refresh_co_changes call is checked against it from then on.
Questions about refresh_co_changes
Rebuild co-change index from git history. Mutates the co-change index; idempotent. Use after significant git history changes. Returns JSON: { status, pairs_stored, window_days }. It is categorised as a Write tool in the Trace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trace MCP server in PolicyLayer and add a rule for refresh_co_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 Trace. Nothing to install.
refresh_co_changes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the refresh_co_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 refresh_co_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.
refresh_co_changes is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
This server
Across the catalogue