List the last N DAG nodes (sporocarps) in the substrate
AI agents call myco_query_recent_nodes 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 queries and lists historical nodes from a directed acyclic graph (DAG) data structure. The verb 'List' and action of retrieving recent nodes are characteristic of Read operations. There is no indication the tool modifies, deletes, executes external operations, or commits financial actions.
From the tool's definition Tool name includes 'query' and description states 'List the last N DAG nodes' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List the last N DAG nodes (sporocarps) in 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_query_recent_nodes: 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_query_recent_nodes 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_query_recent_nodes 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_query_recent_nodes. 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_query_recent_nodes 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 →