Find source files with no corresponding belief in the vault. Scans a directory for source files (.py, .rs, .ts, .js) and checks which ones have no belief artifact. Useful for identifying blind spots before running compile_beliefs. Args: directory: Path to scan. Defaults to the project root.
AI agents call coverage_gaps to retrieve information from Entroly Context Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing data (file system state and belief vault) to identify gaps. It does not create, modify, delete, or execute anything - it only reads and reports findings. The blast radius of misuse is minimal since the worst outcome is incorrect gap identification, which does not affect system state.
From the tool's definition Tool description states it 'Scans a directory' and 'checks which ones have no belief artifact' - these are query/inspection operations with no modification or execution.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access coverage_gaps gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Entroly Context Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for coverage_gaps:
{
"version": "1",
"default": "deny",
"tools": {
"coverage_gaps": {}
}
}coverage_gaps 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.
Find source files with no corresponding belief in the vault. Scans a directory for source files (.py, .rs, .ts, .js) and checks which ones have no belief artifact. Useful for identifying blind spots before running compile_beliefs. Args: directory: Path to scan. Defaults to the project root. It is categorised as a Read tool in the Entroly Context Engine MCP Server, which means it retrieves data without modifying state.
Register the Entroly Context Engine MCP server in PolicyLayer and add a rule for coverage_gaps: 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 Entroly Context Engine. Nothing to install.
coverage_gaps 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 coverage_gaps 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 coverage_gaps. 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.
coverage_gaps is provided by the Entroly Context Engine MCP server (juyterman1000/entroly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Entroly Context Engine, 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.
52 Entroly Context Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.