AI agents call get_module_detail 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 retrieves details about modules from the local-first index. No evidence suggests it modifies data, executes code, deletes content, or moves money. It functions as a targeted query/retrieval mechanism similar to other read-only tools on the ContextCore server. The main risk is information disclosure (low severity), which is typical for read operations over indexed local files.
From the tool's definition Tool name 'get_module_detail' combined with server context showing tools like 'get_file_content', 'get_codebase_context', and 'fetch_content' that retrieve indexed data.
Documented attack patterns abuse exactly the kind of access get_module_detail 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_module_detail:
{
"version": "1",
"default": "deny",
"tools": {
"get_module_detail": {}
}
}get_module_detail 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.
Targeted module detail tool. 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_module_detail: 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_module_detail 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_module_detail 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_module_detail. 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_module_detail 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.