myco_register_axis | PolicyLayer

WHAT IT DOES

What myco_register_axis does on Myco — Agent-First Cognitive Substrate

AI agents use myco_register_axis 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.

WHY IT NEEDS A POLICY

Why myco_register_axis needs a policy

This tool creates or modifies substrate configuration by registering a new axis—a reversible write operation. While it affects the behavior of an agent cognitive substrate (medium severity due to potential downstream effects on agent decision-making), it does not execute arbitrary code, delete data irreversibly, or move money.

From the tool's definition Tool name 'myco_register_axis' and description 'Register a new gradient axis' indicate creation/addition of a new entity (axis) to the substrate. The phrase 'Axes are operator-defined channels' confirms this is user-initiated configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

myco_register_axis Rate-limited

myco_register_axis stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "myco_register_axis": {
      "limits": [
        {
          "counter": "myco_register_axis_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Myco — Agent-First Cognitive Substrate, so you can run agents against it safely.

FAQ

Questions about myco_register_axis

What does the myco_register_axis tool do? +

Register a new gradient axis on the substrate. Axes are operator-defined channels through which deltas accumulate; when an axis crosses its fruiting threshold, the substrate emits a sporocarp. 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.

How do I enforce a policy on myco_register_axis? +

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

myco_register_axis is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit myco_register_axis? +

Yes. Add a rate_limit block to the myco_register_axis 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 myco_register_axis completely? +

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

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