substrate_info

Report substrate version + Python kernel/tropism version + Python interpreter version. Useful for verifying which substrate stack is live in this session.

Category Read
Risk class Low
Parameters 00 required

What substrate_info does on Myco — Agent-First Cognitive Substrate

AI agents call substrate_info 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.

Why substrate_info needs a policy

This tool queries and returns version information about the running substrate and Python environment. It performs pure information retrieval with no state mutation, no code execution beyond introspection, and no destructive or financial operations. The blast radius of misuse is minimal—an agent gaining access to version numbers poses negligible security risk.

From the tool's definition Tool name 'substrate_info' and description 'Report substrate version + Python kernel/tropism version + Python interpreter version' indicates retrieval of system metadata with no modification or side effects.

Questions about substrate_info

What does the substrate_info tool do? +

Report substrate version + Python kernel/tropism version + Python interpreter version. Useful for verifying which substrate stack is live in this session. It is categorised as a Read tool in the Myco — Agent-First Cognitive Substrate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on substrate_info? +

Register the Myco — Agent-First Cognitive Substrate MCP server in PolicyLayer and add a rule for substrate_info: 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.

What risk level is substrate_info? +

substrate_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit substrate_info? +

Yes. Add a rate_limit block to the substrate_info 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.

How do I block substrate_info completely? +

Set action: deny in the PolicyLayer policy for substrate_info. 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.

What MCP server provides substrate_info? +

substrate_info 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.