Find a machine/device in Microsoft Defender by hostname. Returns device details including health status, risk score, exposure level, and device ID.
AI agents call get_machine_by_name 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.
get_machine_by_name queries Microsoft Defender for device information and returns read-only data (health status, risk score, exposure level, device ID). This is a lookup/retrieval operation with no capability to modify state, execute actions, or cause irreversible changes. While the context involves security operations, the tool itself performs only information retrieval, fitting the Read category.
From the tool's definition Tool 'find a machine/device' and 'returns device details' — purely retrieves information without modification, deletion, or execution. No side effects.
Documented attack patterns abuse exactly the kind of access get_machine_by_name 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_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"get_machine_by_name": {}
}
}get_machine_by_name 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.
Find a machine/device in Microsoft Defender by hostname. Returns device details including health status, risk score, exposure level, and device ID. 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_by_name: 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_by_name 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_by_name 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_by_name. 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_by_name 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.