Enumerate DAG node hashes added since a given prev_tip (or from genesis if omitted), with full per-node metadata so the caller can independently reconstruct the substrate
AI agents call myco_enumerate_dag_since to retrieve information from Myco — Agent-First Cognitive Substrate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and exposes internal graph/DAG structure and metadata from the cognitive substrate. While it is a Read operation (no data modification), the severity is elevated to medium because enumerating the complete internal architecture and metadata of an agent's cognitive substrate could enable an adversary to understand the agent's reasoning state, reconstruct private decision trees, or identify…
From the tool's definition Tool description states it "Enumerate[s] DAG node hashes...with full per-node metadata so the caller can independently reconstruct the substrate".
Attacks that exploit this kind of access
Enumerate DAG node hashes added since a given prev_tip (or from genesis if omitted), with full per-node metadata so the caller can independently reconstruct the substrate. It is categorised as a Read tool in the Myco — Agent-First Cognitive Substrate MCP Server, which means it retrieves data without modifying state.
Register the Myco — Agent-First Cognitive Substrate MCP server in PolicyLayer and add a rule for myco_enumerate_dag_since: 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.
myco_enumerate_dag_since 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 myco_enumerate_dag_since 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 myco_enumerate_dag_since. 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.
myco_enumerate_dag_since 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →