recommend
AI agents call recommend as a supporting operation in AWS IoT SiteWise MCP Server workflows.
With no description available, the tool name 'recommend' suggests a read/advisory operation that provides suggestions rather than executing actions, but confidence is very low due to lack of description. Defaulting to Other with low severity given the passive connotation of the name.
From the tool's definition Tool name is 'recommend' and description is empty or uninformative.
Attacks that exploit this kind of access
recommend. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for recommend: 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.
recommend is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the recommend 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 recommend. 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.
recommend 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.