disconnect
AI agents call disconnect as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The tool name 'disconnect' in an AWS IoT SiteWise context could mean disconnecting a device, gateway, or data stream. This could be disruptive (e.g., severing an IoT connection) but may also be reversible (reconnect is possible). Without a description, it's unclear if this is Execute, Write, or Destructive. Given the ambiguity and empty description, confidence is low.
From the tool's definition Tool name is 'disconnect' but description is empty or uninformative; no further context available.
Attacks that exploit this kind of access
disconnect. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for disconnect: 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.
disconnect is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the disconnect 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 disconnect. 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.
disconnect 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.