Get all context for a file (sessions, decisions, mistakes, commits)
AI agents call get_file_context 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 purely retrieves and queries data about a file's context—its sessions, decisions, mistakes, and commits. It has no side effects, does not modify data, execute code, delete content, or affect financial systems. The verb 'Get' and the read-only nature of retrieving existing context places it squarely in the Read category with low severity.
From the tool's definition Tool description states it 'Get[s] all context for a file' without any modification, creation, deletion, or execution capability. The retrieval of sessions, decisions, mistakes, and commits represents querying existing metadata and history.
Documented attack patterns abuse exactly the kind of access get_file_context 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 get_file_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_file_context": {}
}
} get_file_context 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.
Get all context for a file (sessions, decisions, mistakes, commits). 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 get_file_context: 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.
get_file_context 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_file_context 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_file_context. 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_file_context 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.