myco_perturb_axis | PolicyLayer

WHAT IT DOES

What myco_perturb_axis does on Myco — Agent-First Cognitive Substrate

AI agents use myco_perturb_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_perturb_axis needs a policy

The tool modifies a registered axis by applying a delta value, which is a write/update operation on the cognitive substrate's internal state. It does not appear to irreversibly destroy data, execute code, or involve financial transactions. However, since it is described as an 'operator-side input channel,' misuse could meaningfully alter the substrate's behavior — hence medium severity.

From the tool's definition Apply a delta (positive or negative) to a registered axis. This is the operator-side input channel into the substrate

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

myco_perturb_axis Rate-limited

myco_perturb_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_perturb_axis": {
      "limits": [
        {
          "counter": "myco_perturb_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_perturb_axis

What does the myco_perturb_axis tool do? +

Apply a delta (positive or negative) to a registered axis. This is the operator-side input channel into the substrate. 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_perturb_axis? +

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

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

Can I rate-limit myco_perturb_axis? +

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

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

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