Show a summary of all saved knowledge: how many contexts are stored, broken down by surface (Chat/Code/Cowork) and type (decisions, preferences, insights, etc.), database size, and date range. Use when the user asks
AI agents call bridge_status 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 retrieves and presents metadata about the persistent memory system (counts, sizes, date ranges) without creating, modifying, or deleting any data. It is a read operation with no side effects, making it the lowest-risk category. The low severity reflects that misuse would only expose non-sensitive system statistics.
From the tool's definition Tool name 'bridge_status' and description 'Show a summary' indicates a read-only operation that queries and displays aggregate statistics about stored contexts without modifying data. No mutations, deletions, or side effects are described.
Documented attack patterns abuse exactly the kind of access bridge_status 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_status:
{
"version": "1",
"default": "deny",
"tools": {
"bridge_status": {}
}
}bridge_status 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.
Show a summary of all saved knowledge: how many contexts are stored, broken down by surface (Chat/Code/Cowork) and type (decisions, preferences, insights, etc.), database size, and date range. Use when the user asks. 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_status: 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_status 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_status 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_status. 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_status 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.