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

WHAT IT DOES

What setup does on AWS IoT SiteWise MCP Server

AI agents call setup as a supporting operation in AWS IoT SiteWise MCP Server workflows.

WHY IT NEEDS A POLICY

Why setup needs a policy

The description is empty and uninformative. The name 'setup' could imply configuration, initialization, or resource provisioning — which could span Write, Execute, or other categories. Without further context, classification is highly uncertain. Defaulting to 'Other' with low confidence due to lack of evidence.

From the tool's definition Tool name is 'setup' with an empty description, providing no information about what it does.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup Rate-limited

setup gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup": {
      "limits": [
        {
          "counter": "setup_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR 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 setup

What does the setup tool do? +

setup. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on setup? +

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

setup is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit setup? +

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

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

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