Set multiple values in the cache (alias for set_many).
AI agents use cache_set_multi to create or update resources in Amazon SageMaker AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon SageMaker AI MCP Server environment.
This tool writes to a cache by setting multiple values, which is a reversible operation (values can be overwritten or cleared). It does not read data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).
From the tool's definition Tool name 'cache_set_multi' and description 'Set multiple values in the cache' indicate creation or modification of cached data. The phrase 'Set multiple values' is a write operation.
Attacks that exploit this kind of access
Set multiple values in the cache (alias for set_many). It is categorised as a Write tool in the Amazon SageMaker AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for cache_set_multi: 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 SageMaker AI MCP Server. Nothing to install.
cache_set_multi 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 cache_set_multi 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 cache_set_multi. 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.
cache_set_multi is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.