List recent machine actions (response actions) from Microsoft Defender. Can filter by device, action type, or status.
AI agents call get_machine_actions to retrieve information from Response MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about response actions that have already been executed. It performs filtering and listing operations with no side effects, state changes, or ability to trigger new actions. Despite the security-sensitive context (Microsoft Defender XDR), the tool itself only reads data, making it a Read category risk with low severity.
From the tool's definition Tool description explicitly states 'List recent machine actions' and 'Can filter by device, action type, or status' — these are read-only operations that query and retrieve data without modifying or executing actions.
Documented attack patterns abuse exactly the kind of access get_machine_actions 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 get_machine_actions:
{
"version": "1",
"default": "deny",
"tools": {
"get_machine_actions": {}
}
}get_machine_actions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List recent machine actions (response actions) from Microsoft Defender. Can filter by device, action type, or status. It is categorised as a Read tool in the Response MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Response MCP Server MCP server in PolicyLayer and add a rule for get_machine_actions: 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.
get_machine_actions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_machine_actions 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 get_machine_actions. 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.
get_machine_actions 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.