Move member from one set to another.
AI agents use set_move to create or update resources in Amazon Bedrock Knowledge Base Retrieval MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Bedrock Knowledge Base Retrieval MCP Server environment.
This tool modifies data (set membership) but the operation is reversible—members can be moved back or adjusted. It does not delete data permanently, execute arbitrary code, move money, or trigger destructive actions.
From the tool's definition Tool name 'set_move' and description 'Move member from one set to another' indicate modification of set membership state through a reversible operation.
Documented attack patterns abuse exactly the kind of access set_move gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Bedrock Knowledge Base Retrieval MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_move:
{
"version": "1",
"default": "deny",
"tools": {
"set_move": {
"limits": [
{
"counter": "set_move_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_move stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
All 805 Amazon Bedrock Knowledge Base Retrieval MCP Server tools →
Move member from one set to another. It is categorised as a Write tool in the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon Bedrock Knowledge Base Retrieval 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 Amazon Bedrock Knowledge Base Retrieval 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 Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server (awslabs.bedrock-kb-retrieval-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Bedrock Knowledge Base Retrieval MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Amazon Bedrock Knowledge Base Retrieval MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.