knitbrain_record_false_positive

WHAT IT DOES

What knitbrain_record_false_positive does on Knitbrain

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

WHY IT NEEDS A POLICY

Why knitbrain_record_false_positive needs a policy

This tool records feedback/corrections about misclassifications, writing data that influences the classifier over time. It is a Write operation (creating a correction record) with limited blast radius; misuse could gradually skew classifier behavior but is reversible and low-impact.

From the tool's definition 'Record it: claimed tier vs what the task actually was. After 3 same-direction reports the classifier' — the tool writes a false-positive report to correct classifier behavior

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

knitbrain_record_false_positive Rate-limited

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

FAQ

Questions about knitbrain_record_false_positive

What does the knitbrain_record_false_positive tool do? +

The classifier got it wrong? Record it: claimed tier vs what the task actually was. After 3 same-direction reports the classifier. It is categorised as a Write tool in the Knitbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on knitbrain_record_false_positive? +

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

What risk level is knitbrain_record_false_positive? +

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

Can I rate-limit knitbrain_record_false_positive? +

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

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

knitbrain_record_false_positive is provided by the Knitbrain MCP server (pdgit12/knitbrain). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.