Sync all context files (claude.md, gemini.md, agents.md, .cursor/context.md) without closing the session. Useful for mid-session syncs.
AI agents use sync_context_files to create or update resources in MCP Session Closer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Session Closer environment.
This tool modifies context files and syncing operations across multiple files (claude.md, gemini.md, agents.md, .cursor/context.md), which constitute Write operations. The changes are committed to git and reversible through standard version control.
From the tool's definition Tool performs 'sync all context files' and 'update Agent OS files' - operations that modify stored data. The server description explicitly mentions 'updating Agent OS files' and 'automatically committing changes to git', indicating reversible data…
Attacks that exploit this kind of access
Sync all context files (claude.md, gemini.md, agents.md, .cursor/context.md) without closing the session. Useful for mid-session syncs. It is categorised as a Write tool in the MCP Session Closer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Session Closer MCP server in PolicyLayer and add a rule for sync_context_files: 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 MCP Session Closer. Nothing to install.
sync_context_files 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 sync_context_files 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 sync_context_files. 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.
sync_context_files is provided by the MCP Session Closer MCP server (tylarcam/mcp-session-closer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
sync_context_files is one line of MCP Session Closer's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →