rename · AWS IoT SiteWise MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename does on AWS IoT SiteWise MCP Server

AI agents use rename 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 rename needs a policy

The 'rename' operation modifies existing data (asset/resource names) but remains reversible—the original name can be restored. This places it in the Write category rather than Read (no side effects) or Destructive (irreversible). Medium severity reflects that widespread renaming could cause operational confusion or break dependent references, but the change itself is undoable.

From the tool's definition Tool name 'rename' in AWS IoT SiteWise context indicates modification of resource metadata or properties. The empty description prevents full certainty, but renaming is a reversible write operation typical of AWS resource management.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename Rate-limited

rename 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": {
    "rename": {
      "limits": [
        {
          "counter": "rename_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 rename

What does the rename tool do? +

rename. 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 rename? +

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

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

Can I rate-limit rename? +

Yes. Add a rate_limit block to the rename 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 rename completely? +

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

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