report_failure · Netlab MCP: Risk & Policy

WHAT IT DOES

What report_failure does on Netlab

AI agents use report_failure to create or update resources in Netlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Netlab environment.

WHY IT NEEDS A POLICY

Why report_failure needs a policy

This tool writes/updates data in the compatibility matrix by recording a failure result. It modifies stored data but does not irreversibly delete anything, execute code, or involve financial transactions. Misuse could corrupt the compatibility knowledge base, leading to incorrect network configurations being generated or valid ones being rejected.

From the tool's definition Record a negative result (a combo that did not work) into the compatibility matrix

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

report_failure Rate-limited

report_failure 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": {
    "report_failure": {
      "limits": [
        {
          "counter": "report_failure_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 Netlab, so you can run agents against it safely.

FAQ

Questions about report_failure

What does the report_failure tool do? +

Record a negative result (a combo that did not work) into the compatibility matrix. It is categorised as a Write tool in the Netlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on report_failure? +

Register the Netlab MCP server in PolicyLayer and add a rule for report_failure: 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 Netlab. Nothing to install.

What risk level is report_failure? +

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

Can I rate-limit report_failure? +

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

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

report_failure is provided by the Netlab MCP server (steinzi/netlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

report_failure is one line of Netlab's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →