Read all context information (rules, branch memory bank, global memory bank) at once
AI agents call read_context to retrieve information from Memory Bank MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored context information (rules, branch memory bank, global memory bank) without modifying, deleting, or executing anything. It has no side effects beyond data access. The blast radius of misuse is minimal—an agent could read stored documentation and rules, but cannot alter, delete, or act upon them. Classified as Read with low severity.
From the tool's definition Tool name is 'read_context' and description states 'Read all context information' — the verb 'read' and lack of any modification, deletion, or execution semantics clearly indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access read_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory Bank MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read_context:
{
"version": "1",
"default": "deny",
"tools": {
"read_context": {}
}
}read_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.
Read all context information (rules, branch memory bank, global memory bank) at once. It is categorised as a Read tool in the Memory Bank MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Memory Bank MCP Server MCP server in PolicyLayer and add a rule for read_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 Memory Bank MCP Server. Nothing to install.
read_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 read_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 read_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.
read_context is provided by the Memory Bank MCP Server MCP server (t3ta/memory-bank-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memory Bank MCP Server, 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.
4 Memory Bank MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.