// MCP TOOL REFERENCE

epistemic_route

ServerEntroly Context Engine
CategoryExecute

WHAT IT DOES

What epistemic_route does on Entroly Context Engine

AI agents invoke epistemic_route to trigger actions in Entroly Context Engine. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

Why epistemic_route needs a policy

This tool executes a routing/orchestration operation that inspects signals and triggers downstream flows (Belief → Action, Verification → Action, etc.). It is not a simple read — it actively dispatches processing pipelines and can trigger actions and evolution cycles. The description is partially truncated ('C'), reducing confidence slightly.

From the tool's definition 'Route a query through the CogOps Epistemic Ingress Controller' — selects and triggers one of 5 canonical flows including actions, verification steps, truth compilation, and self-improvement cycles

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

POLICY

How to control epistemic_route

PolicyLayer is an MCP gateway — it sits between your AI agents and Entroly Context Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for epistemic_route:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "epistemic_route": {
      "limits": [
        {
          "counter": "epistemic_route_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

epistemic_route stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Entroly Context Engine tools

Execute execute_flow Execute a full canonical epistemic flow end-to-end. Routes the query through the Execute start_workspace_listener Start a background workspace listener that continuously feeds repo changes into CogOps. Execute process_change Process a code change through the Change-Driven pipeline (Flow ④). Full pipeline: Execute manage_skills Manage the CogOps skill lifecycle (Evolution layer). Actions: - list: Sho Write compile_docs Compile markdown documentation files into belief artifacts. Ingests project-level Write ingest_diagram Ingest an architecture or flow diagram into the context memory. Converts Mermaid, Write ingest_voice Ingest a voice/meeting transcript into the context memory. Converts pre-transcrib Write record_ci_result record_ci_result

All 52 Entroly Context Engine tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Entroly Context Engine → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about epistemic_route

What does the epistemic_route tool do? +

Route a query through the CogOps Epistemic Ingress Controller. Inspects 4 signals (intent, belief coverage, freshness, risk) and selects one of 5 canonical flows: ① Fast Answer: Belief → Action (fresh, verified, low-risk) ② Verify Before Answer: Belief → Verification → Action (stale/risky) ③ Compile On Demand: Truth → Belief → Verification → Action (no beliefs) ④ Change-Driven: Event → Truth → Belief → ... (PR/commit/incident) ⑤ Self-Improvement: Misses → Evolution → Belief (repeated failures) Call this BEFORE optimize_context to understand how the system should approach your query. Existing tools work exactly as before. Args: query: The user query or event description is_event: True if this is a change-driven event (PR, commit, etc.) event_type: Type of event (pr, commit, release, incident, scheduled). It is categorised as a Execute tool in the Entroly Context Engine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on epistemic_route? +

Register the Entroly Context Engine MCP server in PolicyLayer and add a rule for epistemic_route: 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 Entroly Context Engine. Nothing to install.

What risk level is epistemic_route? +

epistemic_route is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit epistemic_route? +

Yes. Add a rate_limit block to the epistemic_route 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 epistemic_route completely? +

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

epistemic_route is provided by the Entroly Context Engine MCP server (juyterman1000/entroly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.