suggest_aws_commands
AI agents call suggest_aws_commands as a supporting operation in AWS IoT SiteWise MCP Server workflows.
With no description available, classification relies solely on the tool name. 'Suggest' implies a read-like or advisory operation that generates recommendations without executing them. However, confidence is low due to the empty description. If the tool actually executes commands, it would be reclassified as Execute or higher.
From the tool's definition Tool description is empty and uninformative; the name 'suggest_aws_commands' implies providing suggestions or recommendations rather than executing actions.
Attacks that exploit this kind of access
suggest_aws_commands. 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 suggest_aws_commands: 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.
suggest_aws_commands 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 suggest_aws_commands 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 suggest_aws_commands. 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.
suggest_aws_commands 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.