List recent immune events recorded by the substrate
AI agents call myco_query_immune_events 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 historical event logs from the cognitive substrate's internal immune system. It performs a passive query operation that returns data without altering state, creating new records, executing external code, or destroying data. The blast radius of misuse is minimal—an agent could read operational logs but cannot cause structural damage or invoke unwanted actions through this interface alone.
From the tool's definition Tool name includes 'query' and description states 'List recent immune events' — both indicate a read-only retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List recent immune events recorded by 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_immune_events: 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_immune_events 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_immune_events 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_immune_events. 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_immune_events 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 →