kb_list
List recent entries with optional filters by kind, tag, or date.
This record as markdown: /tools/0x67108864-persistent-kb-mcp/kb-list.md
What kb_list does on Persistent Kb
AI agents call kb_list to retrieve information from Persistent Kb without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why kb_list is rated Low
The tool retrieves and displays knowledge base entries with optional filtering. It performs no side effects, creates no new data, executes no code, and does not delete or move money. It is purely a read operation to query and view stored information.
From the tool's definition Tool name is 'kb_list' and description states 'List recent entries with optional filters by kind, tag, or date' — this is a query/retrieval operation that returns data without modifying or deleting it.
Attacks that exploit this kind of access
The rule that runs kb_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Persistent Kb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kb_list, this is the rule to start with:
kb_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Persistent Kb, apply this rule, and every kb_list call is checked against it from then on.
Questions about kb_list
List recent entries with optional filters by kind, tag, or date. It is categorised as a Read tool in the Persistent Kb MCP Server, which means it retrieves data without modifying state.
Register the Persistent Kb MCP server in PolicyLayer and add a rule for kb_list: 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 Persistent Kb. Nothing to install.
kb_list 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 kb_list 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 kb_list. 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.
kb_list is provided by the Persistent Kb MCP server (0x67108864/persistent-kb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Persistent Kb, and thousands of servers like it.
This server
Across the catalogue