Initiate a Microsoft Defender Antivirus scan on a device. Quick scan checks common malware locations, Full scan checks entire disk.
AI agents invoke run_antivirus_scan 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 executes a scan operation on a device, which is an active intervention that triggers external security software. While not destructive (scans don't delete data), it is clearly an execution action that launches a process with real-world effects.
From the tool's definition Initiates a Microsoft Defender Antivirus scan on a device"; the tool triggers an external security operation whose effects depend on arguments (Quick scan vs. Full scan selection and target device).
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access run_antivirus_scan 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 run_antivirus_scan:
{
"version": "1",
"default": "deny",
"tools": {
"run_antivirus_scan": {
"limits": [
{
"counter": "run_antivirus_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_antivirus_scan 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.
Initiate a Microsoft Defender Antivirus scan on a device. Quick scan checks common malware locations, Full scan checks entire disk. 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 run_antivirus_scan: 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.
run_antivirus_scan 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 run_antivirus_scan 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 run_antivirus_scan. 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.
run_antivirus_scan 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.