Low Risk

get_file_context

Get all context for a file (sessions, decisions, mistakes, commits)

How to control get_file_context ↓

What get_file_context does on Claude Writer's Aid MCP

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.

Low Risk

Why get_file_context needs a policy

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:

How to control get_file_context

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:

policy.json
{
  "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.

  1. Create a free account and register Claude Writer's Aid MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_file_context

What does the get_file_context tool do? +

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.

How do I enforce a policy on get_file_context? +

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.

What risk level is get_file_context? +

get_file_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_file_context? +

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.

How do I block get_file_context completely? +

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.

What MCP server provides get_file_context? +

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.

Enforce policy on every Claude Writer's Aid MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.