Pop value(s) from left of list.
AI agents call list_pop_left to permanently remove resources in AWS IoT SiteWise MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
'Pop' operations remove data from a data structure — the value is consumed/removed from the list, which is an irreversible destructive modification. However, the description is minimal and the tool appears on an AWS IoT SiteWise MCP server, which is an unusual context for a list pop operation (possibly a Redis-style or queue operation).
From the tool's definition Pop value(s) from left of list
Attacks that exploit this kind of access
Pop value(s) from left of list. It is categorised as a Destructive tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for list_pop_left: 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_pop_left is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the list_pop_left 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_pop_left. 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_pop_left 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.