Isolate a device from the network to prevent lateral movement. Use Full isolation to block all connections, or Selective to allow Outlook/Teams/Skype.
AI agents invoke isolate_device to trigger actions in Response MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers a real-world network isolation action on a device via Microsoft Defender XDR. It is an external operational action (not merely data retrieval or a local write), and misuse could cut off a critical system from the network entirely. Full isolation blocks all connections, making this high-impact and potentially disruptive, warranting critical severity.
From the tool's definition Isolate a device from the network to prevent lateral movement. Use Full isolation to block all connections, or Selective to allow Outlook/Teams/Skype.
Documented attack patterns abuse exactly the kind of access isolate_device gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Response MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for isolate_device:
{
"version": "1",
"default": "deny",
"tools": {
"isolate_device": {
"limits": [
{
"counter": "isolate_device_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}isolate_device stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Isolate a device from the network to prevent lateral movement. Use Full isolation to block all connections, or Selective to allow Outlook/Teams/Skype. It is categorised as a Execute tool in the Response MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Response MCP Server MCP server in PolicyLayer and add a rule for isolate_device: 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 Response MCP Server. Nothing to install.
isolate_device is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the isolate_device 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 isolate_device. 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.
isolate_device is provided by the Response MCP Server MCP server (markolauren/responsemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Response MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Response MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.