get_query_status
AI agents call get_query_status 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.
Status queries are inherently read-only operations that retrieve current state of an existing query without side effects. Absence of description lowers confidence slightly, but the naming convention is unambiguous. Low severity because status retrieval poses minimal risk even if queried maliciously—it reveals state information but cannot modify or delete data, execute code, or trigger external operations.
From the tool's definition Tool name 'get_query_status' indicates a status retrieval operation. No description provided, but the verb 'get' and noun 'status' strongly suggest querying state information without modification.
Attacks that exploit this kind of access
get_query_status. 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 get_query_status: 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.
get_query_status 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 get_query_status 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 get_query_status. 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.
get_query_status 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.