Move member from one set to another.
AI agents use set_move to create or update resources in AWS IoT SiteWise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS IoT SiteWise MCP Server environment.
The tool modifies membership associations by moving an entity between sets, which constitutes a Write operation. It is reversible (the member can be moved back), so it does not qualify as Destructive. The blast radius is medium because incorrect moves could disrupt organizational structures or access controls, but the change is not permanent and not financial.
From the tool's definition Tool name 'set_move' and description 'Move member from one set to another' indicate modification of organizational membership or resource grouping. This is a reversible state change operation.
Attacks that exploit this kind of access
Move member from one set to another. It is categorised as a Write tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for set_move: 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.
set_move is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_move 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 set_move. 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.
set_move 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.