Stop a running process and quarantine the associated file on a device. Requires the SHA1 hash of the file.
AI agents invoke stop_and_quarantine 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.
The tool directly executes an operational action on a target device (stopping processes, quarantining files). While this modifies system state (making it tangentially 'Write-like'), the nature of stopping processes and performing forensic quarantine actions classifies it as Execute because it triggers external operations with state-dependent effects on target systems.
From the tool's definition Tool performs 'stop a running process and quarantine the associated file on a device' — this executes a direct action on a live system with immediate effects, and is a core incident response capability that modifies system state.
Documented attack patterns abuse exactly the kind of access stop_and_quarantine 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 stop_and_quarantine:
{
"version": "1",
"default": "deny",
"tools": {
"stop_and_quarantine": {
"limits": [
{
"counter": "stop_and_quarantine_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} stop_and_quarantine 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.
Stop a running process and quarantine the associated file on a device. Requires the SHA1 hash of the file. 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 stop_and_quarantine: 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.
stop_and_quarantine 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 stop_and_quarantine 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 stop_and_quarantine. 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.
stop_and_quarantine 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.