AI agents use knitbrain_learning_outcome 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.
The tool writes feedback/outcome data about a recalled learning back to the system, updating its memory or model. This is a reversible data write (logging an outcome). No code execution, deletion, or financial action is involved. Severity is low because the blast radius of misuse is minimal — at worst it corrupts a learning record.
From the tool's definition 'Close the loop on a recalled learning: report whether it actually HELPED on this task' — this records/writes an outcome or feedback signal back to the system
Attacks that exploit this kind of access
Close the loop on a recalled learning: report whether it actually HELPED on this task (a concrete outcome, not. 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.
Register the Knitbrain MCP server in PolicyLayer and add a rule for knitbrain_learning_outcome: 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.
knitbrain_learning_outcome is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the knitbrain_learning_outcome 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.
Set action: deny in the PolicyLayer policy for knitbrain_learning_outcome. 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.
knitbrain_learning_outcome 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.
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 →