bridge_list_contexts

THE RISK

Low Risk

Why bridge_list_contexts needs a policy

This tool performs a read-only operation to list and filter existing contexts from persistent memory. It retrieves information but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could only view stored contexts, not alter or act upon them maliciously.

From the tool's definition Tool name 'bridge_list_contexts' and description 'Browse and filter all saved contexts' indicate data retrieval without modification. No language suggesting deletion, modification, execution, or financial impact.

Documented attack patterns abuse exactly the kind of access bridge_list_contexts gives an agent:

POLICY

How to control bridge_list_contexts

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_list_contexts:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bridge_list_contexts": {}
  }
}

bridge_list_contexts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Acheron — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Acheron tools

Destructive bridge_delete_context Permanently delete a saved context. Use when the user says Write bridge_save_context Remember something for later. Use this when the user says things like Read bridge_get_context Retrieve the full details of a previously saved context by its ID. Use this after finding Read bridge_search_context Search through everything that has been saved across conversations. Use when the user asks Read bridge_status Show a summary of all saved knowledge: how many contexts are stored, broken down by surfac

All 6 Acheron tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about bridge_list_contexts

What does the bridge_list_contexts tool do? +

Browse and filter all saved contexts. 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.

How do I enforce a policy on bridge_list_contexts? +

Register the Acheron MCP server in PolicyLayer and add a rule for bridge_list_contexts: 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.

What risk level is bridge_list_contexts? +

bridge_list_contexts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bridge_list_contexts? +

Yes. Add a rate_limit block to the bridge_list_contexts 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.

How do I block bridge_list_contexts completely? +

Set action: deny in the PolicyLayer policy for bridge_list_contexts. 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.

What MCP server provides bridge_list_contexts? +

bridge_list_contexts 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.

Enforce policy on every Acheron tool call.

Start from Acheron, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →