cache_replace · AWS IoT SiteWise MCP Server MCP

WHAT IT DOES

What cache_replace does on AWS IoT SiteWise MCP Server

AI agents use cache_replace 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.

WHY IT NEEDS A POLICY

Why cache_replace needs a policy

The tool modifies existing cached values, which is a reversible write operation. Severity is medium rather than high because: (1) cache data is typically temporary/non-persistent, (2) the conditional existence check prevents some misuse patterns, and (3) the blast radius is limited to cached application state rather than permanent data stores.

From the tool's definition Tool description states 'Replace a value in the cache' — this modifies cached data. The conditional 'only if the key exists' makes it safer than unconditional overwrites, but it still performs a Write operation on stored data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cache_replace Rate-limited

cache_replace 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cache_replace": {
      "limits": [
        {
          "counter": "cache_replace_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AWS IoT SiteWise MCP Server, so you can run agents against it safely.

FAQ

Questions about cache_replace

What does the cache_replace tool do? +

Replace a value in the cache only if the key exists. 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.

How do I enforce a policy on cache_replace? +

Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for cache_replace: 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.

What risk level is cache_replace? +

cache_replace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cache_replace? +

Yes. Add a rate_limit block to the cache_replace 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.

How do I block cache_replace completely? +

Set action: deny in the PolicyLayer policy for cache_replace. 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.

What MCP server provides cache_replace? +

cache_replace 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.