ALWAYS CALL THIS FIRST - NO EXCEPTIONS. WHEN TO CALL (check these FIRST before responding): - User asks: optimize, improve, analyze, review, suggest, think, opinion. - User mentions: file name, component name, project, codebase, backend, frontend, infra, devops, CI/CD, docker, config. - User asks...
AI agents call get_context_for_file to retrieve information from Ai Readme without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | The path to get context for (relative to project root). Can be either a FILE path or a DIRECTORY path. Examples: "src/components/Button.tsx", "src/components", |
includeRoot | boolean | — | Whether to include root-level AI_README (default: true) |
projectRoot | string | Yes | The root directory of the project. Use the current working directory (e.g., from environment or pwd). If unsure, pass the project root path. |
excludePatterns | array | — | Glob patterns to exclude when scanning |
Parameters from the server's own tool schema.
This tool queries or retrieves file context data to support analysis and recommendations. It has no side effects, creates no modifications, executes no code, and commits no financial transactions. It is a pure read operation that gathers contextual information from the codebase.
From the tool's definition Tool name 'get_context_for_file' and description indicate it retrieves context information from files. The directive 'ALWAYS CALL THIS FIRST' and the listed triggers (optimize, improve, analyze, review, suggest) all involve information gathering with no…
Risk signalsAccepts file system path (path) · Bulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_context_for_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ai Readme, and nothing reaches the server without passing your rules. This is the rule we recommend for get_context_for_file:
{
"version": "1",
"default": "deny",
"tools": {
"get_context_for_file": {}
}
}get_context_for_file 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.
ALWAYS CALL THIS FIRST - NO EXCEPTIONS. WHEN TO CALL (check these FIRST before responding): - User asks: optimize, improve, analyze, review, suggest, think, opinion. - User mentions: file name, component name, project, codebase, backend, frontend, infra, devops, CI/CD, docker, config. - User asks: "what can", "what should", "how to", "can you", "help me". - User wants to: create, build, add, implement, setup, configure, deploy, migrate, optimize, refactor, improve, analyze, review, suggest, think, opinion. - User selects an option that leads to code changes (e.g., choosing from a list of approaches). - User says: "next step", "next phase", "next section", "continue", "proceed", "go ahead", "start", "do it", "yes" (confirming action). - Before: Write, Edit, TodoWrite, Bash (for build/deploy), suggesting ANY code changes. - When executing a plan, todo, or multi-phase task: call BEFORE each file modification. - After user approves a plan or todo, call this BEFORE the each Write/Edit. IF ANY ABOVE = TRUE → CALL get_context_for_file IMMEDIATELY. MANDATORY: Call this tool BEFORE every code-related response. CALL EVERY TIME - EVERY response that involves code/suggestions MUST start with get_context_for_file. CALL EVERY TIME - even if you called it earlier in this conversation. CALL EVERY TIME - even if working on the same file. CALL EVERY TIME - even within the same section/phase - multiple calls are expected and correct. CALL EVERY TIME - context may have changed or sub-directories may have additional conventions. CALL EVERY TIME - when user confirms or selects an option that will result in code changes. What this tool does: Gets AI_README context showing project conventions that MUST be followed. Why it matters: - Without: Wrong tech (suggest Tailwind when project uses CSS Modules). - With: Suggestions fit existing codebase perfectly. - During plan/todo/phase execution: Context may differ per directory; call before EACH file change. DETECT CONFLICTS: After reading context, if user wants X but AI_README says Y: - This is ARCHITECTURAL DECISION. - Workflow: get_context → update_ai_readme → get_context → Write/Edit. RECORD DECISIONS: When you make architectural decisions during planning or implementation: - Design patterns, API structure, naming conventions, new abstractions. - Call update_ai_readme to record decisions that affect multiple files. - Future code (yours or others) will follow these recorded conventions. It is categorised as a Read tool in the Ai Readme MCP Server, which means it retrieves data without modifying state.
get_context_for_file accepts 4 parameters: path, includeRoot, projectRoot, excludePatterns. Required: path, projectRoot. The full parameter table on this page comes from the server's own tool schema.
Register the Ai Readme MCP server in PolicyLayer and add a rule for get_context_for_file: 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 Ai Readme. Nothing to install.
get_context_for_file 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_context_for_file 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_context_for_file. 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_context_for_file is provided by the Ai Readme MCP server (ai-readme-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ai Readme, 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.
6 Ai Readme tools catalogued and risk-classified — across an index of 43,000+ MCP servers.