Retrieve the full details of a previously saved context by its ID. Use this after finding a context via search or list, when the user wants to see the complete content of a specific saved memory. Typically used as a follow-up:
AI agents call bridge_get_context to retrieve information from Acheron without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing data from the persistent memory system without any side effects. It is a read-only operation analogous to a GET request or SELECT query. No data is created, modified, deleted, or executed. The severity is low as misuse would only expose existing stored context data accessible to the user, with no blast radius for system integrity or external operations.
From the tool's definition Tool name 'bridge_get_context' and description states 'Retrieve the full details of a previously saved context by its ID' — explicit retrieval operation with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access bridge_get_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Acheron, and nothing reaches the server without passing your rules. This is the rule we recommend for bridge_get_context:
{
"version": "1",
"default": "deny",
"tools": {
"bridge_get_context": {}
}
}bridge_get_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.
Retrieve the full details of a previously saved context by its ID. Use this after finding a context via search or list, when the user wants to see the complete content of a specific saved memory. Typically used as a follow-up:. It is categorised as a Read tool in the Acheron MCP Server, which means it retrieves data without modifying state.
Register the Acheron MCP server in PolicyLayer and add a rule for bridge_get_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 Acheron. Nothing to install.
bridge_get_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 bridge_get_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 bridge_get_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.
bridge_get_context is provided by the Acheron MCP server (timmx7/acheron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Acheron, 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.
6 Acheron tools catalogued and risk-classified — across an index of 43,000+ MCP servers.