Compile markdown documentation files into belief artifacts. Ingests project-level docs (README.md, ARCHITECTURE.md, docs/, CONTRIBUTING.md, etc.) into the vault as documentation beliefs with confidence 0.80 (human-authored > machine-inferred code beliefs). Args: directory: Project root to scan. D...
AI agents use compile_docs to create or update resources in Entroly Context Engine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Entroly Context Engine environment.
The tool reads markdown documentation files but its primary effect is writing/creating new belief artifacts in the vault. This is a reversible data creation/modification action (Write), not merely a read. The blast radius is medium since it populates an internal knowledge store that influences AI agent behavior, but does not delete data or execute arbitrary code.
From the tool's definition Ingests project-level docs ... into the vault as documentation beliefs
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access compile_docs 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 compile_docs:
{
"version": "1",
"default": "deny",
"tools": {
"compile_docs": {
"limits": [
{
"counter": "compile_docs_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}compile_docs stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Compile markdown documentation files into belief artifacts. Ingests project-level docs (README.md, ARCHITECTURE.md, docs/, CONTRIBUTING.md, etc.) into the vault as documentation beliefs with confidence 0.80 (human-authored > machine-inferred code beliefs). Args: directory: Project root to scan. Defaults to the project root. max_files: Maximum doc files to process (default: 50). It is categorised as a Write tool in the Entroly Context Engine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Entroly Context Engine MCP server in PolicyLayer and add a rule for compile_docs: 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.
compile_docs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the compile_docs 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 compile_docs. 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.
compile_docs 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.