ListKnowledgeBases
AI agents call ListKnowledgeBases to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'List' prefix strongly suggests a read-only operation that retrieves or enumerates knowledge bases without modifying data. No side effects are indicated by the name. Given the empty description, confidence is moderately high but not maximum. Treat as a basic Read operation with low severity—typical data retrieval with minimal blast radius if misused.
From the tool's definition Tool name 'ListKnowledgeBases' indicates a list/enumerate operation. The description is empty, limiting direct evidence from documentation.
Attacks that exploit this kind of access
ListKnowledgeBases. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for ListKnowledgeBases: 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 Awslabs Valkey. Nothing to install.
ListKnowledgeBases 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 ListKnowledgeBases 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 ListKnowledgeBases. 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.
ListKnowledgeBases is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.