Return full structured Layer 1 + Layer 2 codebase context for agent reasoning.
AI agents call get_codebase_context 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 performs information retrieval on a local codebase index, returning structured context for reasoning purposes. While it may expose sensitive code or intellectual property information (hence medium rather than low severity), it does not create, modify, delete, or execute operations.
From the tool's definition Tool returns 'full structured Layer 1 + Layer 2 codebase context' - it retrieves and queries indexed local files without modifying them. The description uses 'Return' and 'context', indicating retrieval operations.
Documented attack patterns abuse exactly the kind of access get_codebase_context 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_codebase_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_codebase_context": {}
}
}get_codebase_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.
Return full structured Layer 1 + Layer 2 codebase context for agent reasoning. 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_codebase_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 ContextCore. Nothing to install.
get_codebase_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_codebase_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_codebase_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_codebase_context 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.