Create a Context Receipt from a local document file or directory. Supports text-like documents currently handled by the local receipt ingester (.md, .txt, .rst). The result is deterministic and local.
AI agents call create_context_receipt_from_path 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 reads local files (markdown, text, rst) and generates a context receipt from them. It is a read/ingest operation with no side effects beyond creating a local in-memory or cached artifact. The result is described as deterministic and local, suggesting no external writes or destructive actions. Severity is low as it only accesses local document files.
From the tool's definition "Create a Context Receipt from a local document file or directory" and "The result is deterministic and local"
Documented attack patterns abuse exactly the kind of access create_context_receipt_from_path 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 create_context_receipt_from_path:
{
"version": "1",
"default": "deny",
"tools": {
"create_context_receipt_from_path": {}
}
}create_context_receipt_from_path 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.
Create a Context Receipt from a local document file or directory. Supports text-like documents currently handled by the local receipt ingester (.md, .txt, .rst). The result is deterministic and local. 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 create_context_receipt_from_path: 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.
create_context_receipt_from_path 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 create_context_receipt_from_path 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 create_context_receipt_from_path. 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.
create_context_receipt_from_path 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.