Raw source read tool for specific file path and optional line range.
AI agents call get_file_content to retrieve information from ContextCore without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and retrieves file content from disk. It performs no modifications, deletions, code execution, or side effects. It is a straightforward data retrieval operation that fits the Read category. The 'optional line range' parameter further confirms it is a simple retrieval mechanism.
From the tool's definition Tool name 'get_file_content' and description 'Raw source read tool for specific file path and optional line range' indicate retrieval of file content without modification or deletion.
Documented attack patterns abuse exactly the kind of access get_file_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ContextCore, and nothing reaches the server without passing your rules. This is the rule we recommend for get_file_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_file_content": {}
}
}get_file_content 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.
Raw source read tool for specific file path and optional line range. It is categorised as a Read tool in the ContextCore MCP Server, which means it retrieves data without modifying state.
Register the ContextCore MCP server in PolicyLayer and add a rule for get_file_content: 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 ContextCore. Nothing to install.
get_file_content 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_content 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_content. 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_content is provided by the ContextCore MCP server (lucifer-ux/contextcore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ContextCore, 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.
16 ContextCore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.