List all configured AI endpoints available for bridge creation
AI agents call listConfiguredEndpoints to retrieve information from Claude Consciousness Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates configuration data about available endpoints. It performs a passive read operation that returns information without creating side effects, modifying data, or triggering external processes.
From the tool's definition Tool name 'listConfiguredEndpoints' and description 'List all configured AI endpoints available for bridge creation' indicate a query/retrieval operation with no modification of state or execution of external operations.
Documented attack patterns abuse exactly the kind of access listConfiguredEndpoints gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Consciousness Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for listConfiguredEndpoints:
{
"version": "1",
"default": "deny",
"tools": {
"listConfiguredEndpoints": {}
}
}listConfiguredEndpoints 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.
List all configured AI endpoints available for bridge creation. It is categorised as a Read tool in the Claude Consciousness Bridge MCP Server, which means it retrieves data without modifying state.
Register the Claude Consciousness Bridge MCP server in PolicyLayer and add a rule for listConfiguredEndpoints: 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 Claude Consciousness Bridge. Nothing to install.
listConfiguredEndpoints 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 listConfiguredEndpoints 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 listConfiguredEndpoints. 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.
listConfiguredEndpoints is provided by the Claude Consciousness Bridge MCP server (ocean1/mcp_consciousness_bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Consciousness Bridge, 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 Claude Consciousness Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.