P03 §10.4 (Resumable Evolution): Report whether a two-phase schema migration is currently in flight. When an operator submits a schema_evolution mutation with migration_mode=true, the substrate builds a CANDIDATE schema and validates it alongside the active schema for a window of metabolic cycles...
AI agents call myco_query_migration_pending 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 is a pure query/status-check operation. It retrieves metadata about an in-flight schema migration without altering any state. The actual schema evolution (the 'migration_mode=true' submission) is a separate Write or Execute operation; this tool merely reads its progress. The dual-validation window and causal DAG preservation are implementation details that do not elevate the query itself beyond Read category.
From the tool's definition Tool reports status of pending schema migrations: {pending, op, started_at_cycle, window, current_cycle}. Description uses verbs 'Report' and 'reports', indicating retrieval of state information.
Attacks that exploit this kind of access
P03 §10.4 (Resumable Evolution): Report whether a two-phase schema migration is currently in flight. When an operator submits a schema_evolution mutation with migration_mode=true, the substrate builds a CANDIDATE schema and validates it alongside the active schema for a window of metabolic cycles before committing (instead of the default single-cycle apply). This tool reports {pending, op, started_at_cycle, window, current_cycle} — pending=true plus how far through the dual-validation window the migration has progressed. Survives substrate restart (the candidate is resumed from the causal DAG). 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_migration_pending: 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_migration_pending 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_migration_pending 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_migration_pending. 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_migration_pending 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 →