read_document
AI agents call read_document 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 'read_document' function appears to fetch or retrieve document data. Without side effects evident in the name and no description indicating write, execute, or destructive capabilities, this falls into the Read category. Severity is low because retrieving documents poses minimal risk unless the documents contain highly sensitive information—but the tool itself is passive.
From the tool's definition Tool name 'read_document' indicates a retrieval operation. The empty description is uninformative, but the naming convention and sibling tools (which include read-pattern names like 'ActivateAHOReadSets' and 'aggregate') suggest this retrieves or queries data…
Attacks that exploit this kind of access
read_document. 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 read_document: 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.
read_document 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 read_document 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 read_document. 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.
read_document 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.