Retrieves the session-level active context: current work focus, open issues, and recent changes. This is the
AI agents call get_active_context to retrieve information from Engrams without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of session state data. It retrieves context information without creating, modifying, deleting, or executing any operations. The description is slightly cut off but clearly indicates a retrieval/fetch operation. No destructive, financial, or code execution capabilities are present.
From the tool's definition Tool name 'get_active_context' and description 'Retrieves the session-level active context: current work focus, open issues, and recent changes' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_active_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Engrams, and nothing reaches the server without passing your rules. This is the rule we recommend for get_active_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_active_context": {}
}
}get_active_context 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.
Retrieves the session-level active context: current work focus, open issues, and recent changes. This is the. It is categorised as a Read tool in the Engrams MCP Server, which means it retrieves data without modifying state.
Register the Engrams MCP server in PolicyLayer and add a rule for get_active_context: 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 Engrams. Nothing to install.
get_active_context 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_active_context 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_active_context. 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_active_context is provided by the Engrams MCP server (stevebrownlee/engrams). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Engrams, 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.
42 Engrams tools catalogued and risk-classified — across an index of 43,000+ MCP servers.