AI agents call lint to retrieve information from Kb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only analysis operation—it examines notes against compliance rules but does not create, modify, delete, or execute external operations. The blast radius is minimal as it cannot alter state or trigger side effects. Classification as Read is appropriate.
From the tool's definition Tool name 'lint' and description 'Check notes for rule compliance' indicate inspection/validation of existing notes without modification or deletion.
Attacks that exploit this kind of access
Check notes for rule compliance. It is categorised as a Read tool in the Kb MCP Server, which means it retrieves data without modifying state.
Register the Kb MCP server in PolicyLayer and add a rule for 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 Kb. Nothing to install.
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 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 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.
lint is provided by the Kb MCP server (okash1n/kb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
lint is one line of Kb'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 →