SearchRelevantContent
AI agents call SearchRelevantContent 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 strongly suggests a read-only operation (search/query pattern). Without a description, confidence is moderate but the semantic signal is clear that this retrieves or queries data without side effects. In the absence of evidence suggesting write, execute, destructive, or financial operations, Read is the appropriate classification.
From the tool's definition Tool name 'SearchRelevantContent' indicates a search/query operation with no modification or execution implied. No description provided to confirm scope, but naming convention suggests information retrieval.
Attacks that exploit this kind of access
SearchRelevantContent. 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 SearchRelevantContent: 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.
SearchRelevantContent 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 SearchRelevantContent 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 SearchRelevantContent. 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.
SearchRelevantContent 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.