Create a Context Receipt from supplied documents. documents_json may be: - a JSON object mapping source path to text - a JSON array of [source_path, text] pairs - a JSON array of objects with source_path/text or source/content keys The receipt records selected context, omitted relevant context, d...
AI agents use create_context_receipt 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 creates a new structured record (a Context Receipt) from supplied documents. This is a Write operation — it produces/persists a new artifact. It does not execute code, delete data, or involve financial transactions. The description explicitly states 'It does not call an LLM', and the receipt is a metadata/audit record.
From the tool's definition 'Create a Context Receipt from supplied documents' — creates a new artifact (a receipt) recording selected context, omitted relevant context, dependency links, fingerprints, token ratio, warnings, and risk controls
Documented attack patterns abuse exactly the kind of access create_context_receipt 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:
{
"version": "1",
"default": "deny",
"tools": {
"create_context_receipt": {
"limits": [
{
"counter": "create_context_receipt_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_context_receipt 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.
Create a Context Receipt from supplied documents. documents_json may be: - a JSON object mapping source path to text - a JSON array of [source_path, text] pairs - a JSON array of objects with source_path/text or source/content keys The receipt records selected context, omitted relevant context, dependency links, fingerprints, token ratio, warnings, and risk controls. It does not call an LLM. 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 create_context_receipt: 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 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 create_context_receipt 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. 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 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.