myco_run_immune_check

WHAT IT DOES

What myco_run_immune_check does on Myco — Agent-First Cognitive Substrate

AI agents invoke myco_run_immune_check to trigger actions in Myco — Agent-First Cognitive Substrate. 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.

WHY IT NEEDS A POLICY

Why myco_run_immune_check needs a policy

This tool executes a triggered operation ('Trigger an ad-hoc immune verification scan') that initiates internal integrity verification processes and produces observable side effects (emitting immune sporocarp events visible via query tools).

From the tool's definition Trigger an ad-hoc immune verification scan. The substrate runs comprehensive integrity checks...emits a C9 cold_resume_invariant_failure immune sporocarp. Returns a per-check report.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

myco_run_immune_check Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Myco — Agent-First Cognitive Substrate, so you can run agents against it safely.

FAQ

Questions about myco_run_immune_check

What does the myco_run_immune_check tool do? +

Trigger an ad-hoc immune verification scan. The substrate runs comprehensive integrity checks (substrate_id well-formedness, DAG hash-chain integrity, cycle-counter monotonicity, canonical-bytes drift detection, orphan-node detection). For each failed check, the substrate emits a C9 cold_resume_invariant_failure immune sporocarp (visible via myco_query_immune_events). Returns a per-check report. It is categorised as a Execute tool in the Myco — Agent-First Cognitive Substrate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on myco_run_immune_check? +

Register the Myco — Agent-First Cognitive Substrate MCP server in PolicyLayer and add a rule for myco_run_immune_check: 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 Myco — Agent-First Cognitive Substrate. Nothing to install.

What risk level is myco_run_immune_check? +

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

Can I rate-limit myco_run_immune_check? +

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

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

myco_run_immune_check is provided by the Myco — Agent-First Cognitive Substrate MCP server (myco). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.