AI agents call knitbrain_wiki_lint to retrieve information from Knitbrain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes the wiki-brain structure to detect inconsistencies and unused pages, returning diagnostic information. It has no capability to modify data (no write/update operations), delete content (no destructive operations), execute code, or trigger external side effects.
From the tool's definition The tool 'flags claim contradictions' and identifies 'orphan pages' — it performs analysis and health-checking operations that inspect and report on existing data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Health-check the wiki-brain: flags claim contradictions across pages (incl. stale claims superseded over time) and orphan pages nothing links to. It is categorised as a Read tool in the Knitbrain MCP Server, which means it retrieves data without modifying state.
Register the Knitbrain MCP server in PolicyLayer and add a rule for knitbrain_wiki_lint: 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_wiki_lint is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the knitbrain_wiki_lint 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_wiki_lint. 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_wiki_lint 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 →