list_datastores
AI agents call list_datastores 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 'list_' prefix strongly indicates a query/enumeration action that retrieves and returns information without modification. Although the description is empty (reducing confidence slightly), the naming convention and context of a data service make it a Read category tool.
From the tool's definition Tool name 'list_datastores' follows the standard 'list_*' pattern for data retrieval operations. The server is AWS IoT SiteWise, a data management service, making enumeration of datastores a read-only operation.
Attacks that exploit this kind of access
list_datastores. 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 list_datastores: 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.
list_datastores 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 list_datastores 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 list_datastores. 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.
list_datastores 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.