search_by_series_uid
AI agents call search_by_series_uid 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 name indicates a search or lookup function, which is non-destructive and read-only. However, confidence is moderate (0.65) due to the empty description—without explicit documentation, the actual behavior cannot be fully verified. The 'search' verb and 'by_series_uid' qualifier are typical of retrieval operations that retrieve data without side effects.
From the tool's definition Tool name 'search_by_series_uid' suggests a query or retrieval operation targeting medical imaging series by unique identifier. No destructive, write, or execute operations are implied by the name.
Attacks that exploit this kind of access
search_by_series_uid. 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 search_by_series_uid: 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.
search_by_series_uid 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 search_by_series_uid 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 search_by_series_uid. 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.
search_by_series_uid 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.