Run one substrate metabolic cycle. Triggers gradient advance, fruiting checks, and sporocarp emission. Returns the list of fruited axes and the sporocarps emitted (each with type, canonical bytes, and content hash).
AI agents invoke myco_advance_cycle 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.
This tool executes a computational cycle with side effects on the graph substrate state. It is not a simple read operation (which would passively query without state changes) nor a write operation (which would be reversible data modification). Instead, it actively triggers metabolic processes and emits outputs—characteristics of Execute category.
From the tool's definition Tool description states it "Run[s] one substrate metabolic cycle" and "Triggers gradient advance, fruiting checks, and sporocarp emission." The verbs 'run', 'triggers', and 'emission' indicate active state-altering operations.
Attacks that exploit this kind of access
Run one substrate metabolic cycle. Triggers gradient advance, fruiting checks, and sporocarp emission. Returns the list of fruited axes and the sporocarps emitted (each with type, canonical bytes, and content hash). 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.
Register the Myco — Agent-First Cognitive Substrate MCP server in PolicyLayer and add a rule for myco_advance_cycle: 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_advance_cycle is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the myco_advance_cycle 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_advance_cycle. 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_advance_cycle 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 →