Set multiple values in the cache.
AI agents use cache_set_many 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 creates or modifies cached data. It is a Write operation because it stores data in a cache (reversible operation—cached values can be updated or cleared). Severity is medium because cache corruption or malicious cache pollution could affect application behavior, but the impact is generally contained to cached data and typically recoverable.
From the tool's definition Tool name is 'cache_set_many' with description 'Set multiple values in the cache.' The action is to write/set data in a cache system.
Attacks that exploit this kind of access
Set multiple values in the cache. 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_many: 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_many 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_many 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_many. 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_many 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.