Set a value in the cache.
AI agents use cache_set 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.
This tool creates or modifies data (writing to a cache) in a reversible manner. It does not execute code, delete data irreversibly, move money, or trigger external operations with unpredictable effects. The blast radius is limited to cache state, which is typically non-persistent and recoverable.
From the tool's definition Tool name 'cache_set' and description 'Set a value in the cache' indicate a write operation that creates or modifies data in a cache store.
Attacks that exploit this kind of access
Set a value in the cache. 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 cache_set: 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.
cache_set 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 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. 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 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.