ListKnowledgeBases
AI agents call ListKnowledgeBases to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries knowledge base metadata/listings without side effects. The empty description reduces confidence slightly, but the 'List' prefix in AWS APIs conventionally indicates read-only retrieval operations with no data modification or destruction. Blast radius of misuse is low—an AI agent could enumerate knowledge bases but cannot alter or delete data through this operation alone.
From the tool's definition Tool name 'ListKnowledgeBases' indicates retrieval of knowledge base listings; prefix 'List' is a standard AWS pattern for read operations that retrieve collections without modification.
Attacks that exploit this kind of access
ListKnowledgeBases. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server 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 AWS IoT SiteWise MCP Server. 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 AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.