(BETA) Recommends the best LLM models that can run locally on this machine. Requires remote API connection.
AI agents call get_llm_recommendations to retrieve information from Hardware Probe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and provides recommendations based on system analysis and remote API queries. It does not create, modify, delete, execute code, or trigger external operations. It simply reads system state and returns informational recommendations. While it makes a remote API call, the result is a read operation that provides advisory information to the user.
From the tool's definition The tool name 'get_llm_recommendations' and description state it 'Recommends the best LLM models that can run locally on this machine'. The verb 'recommends' indicates retrieval and analysis of data without modification.
Documented attack patterns abuse exactly the kind of access get_llm_recommendations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hardware Probe, and nothing reaches the server without passing your rules. This is the rule we recommend for get_llm_recommendations:
{
"version": "1",
"default": "deny",
"tools": {
"get_llm_recommendations": {}
}
} get_llm_recommendations 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.
(BETA) Recommends the best LLM models that can run locally on this machine. Requires remote API connection. It is categorised as a Read tool in the Hardware Probe MCP Server, which means it retrieves data without modifying state.
Register the Hardware Probe MCP server in PolicyLayer and add a rule for get_llm_recommendations: 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 Hardware Probe. Nothing to install.
get_llm_recommendations 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_llm_recommendations 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_llm_recommendations. 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_llm_recommendations is provided by the Hardware Probe MCP server (@yamaru-eu/hardware-probe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hardware Probe, 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.
11 Hardware Probe tools catalogued and risk-classified — across an index of 43,000+ MCP servers.