Move element from one list to another.
AI agents use list_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.
Moving an element from one list to another is a reversible write operation: it modifies the state of two lists (removes from source, adds to destination). It is not purely destructive since the data is not deleted, but it does alter existing data structures. The description is brief and lacks detail about what 'lists' refer to in the IoT SiteWise context, which reduces confidence slightly.
From the tool's definition 'Move element from one list to another' — moves data between lists, which modifies state in both source and destination lists
Attacks that exploit this kind of access
Move element from one list 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 list_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.
list_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 list_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 list_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.
list_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.