Submit a mutation for the substrate to classify. The substrate classifies via L1/GOVERNANCE rules: daily mutations are auto-accepted; untyped mutations are rejected. Accepted mutations are recorded as DAG nodes (causal history preserved). Rejected mutations trigger immune sporocarp emission (visi...
AI agents use myco_submit_mutation to create or update resources in Myco — Agent-First Cognitive Substrate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Myco — Agent-First Cognitive Substrate environment.
This tool modifies the substrate's internal state by writing new DAG nodes based on submitted mutations. While mutations that are rejected do not persist, accepted ones are permanently recorded in the causal history. The lack of owner attestation verification (noted in the keyless v0.9 update) slightly elevates risk by removing authorization validation.
From the tool's definition 'Submit a mutation for the substrate to classify' and 'Accepted mutations are recorded as DAG nodes' — the tool creates and persists new data structures (DAG nodes) in the cognitive substrate.
Attacks that exploit this kind of access
Submit a mutation for the substrate to classify. The substrate classifies via L1/GOVERNANCE rules: daily mutations are auto-accepted; untyped mutations are rejected. Accepted mutations are recorded as DAG nodes (causal history preserved). Rejected mutations trigger immune sporocarp emission (visible via myco_query_immune_events). (v0.9 keyless: the substrate no longer verifies an owner Ed25519 attestation on CI mutations — classification is content + mutation_type based.). It is categorised as a Write tool in the Myco — Agent-First Cognitive Substrate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Myco — Agent-First Cognitive Substrate MCP server in PolicyLayer and add a rule for myco_submit_mutation: 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_submit_mutation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the myco_submit_mutation 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_submit_mutation. 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_submit_mutation 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 →