(BETA) Checks if a specific LLM model can run on this machine. Returns optimal quantization and estimated tokens per second. Requires remote API connection.
AI agents call check_llm_compatibility 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 queries system capabilities and remote API information to provide compatibility and performance estimates. It performs no writes, deletions, code execution, or financial transactions. The remote API connection is for retrieving diagnostic data, not triggering external operations. The beta status and lack of side effects confirm low severity.
From the tool's definition Tool name 'check_llm_compatibility' and description 'Checks if a specific LLM model can run on this machine. Returns optimal quantization and estimated tokens per second.' indicates data retrieval and analysis without modification.
Documented attack patterns abuse exactly the kind of access check_llm_compatibility 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 check_llm_compatibility:
{
"version": "1",
"default": "deny",
"tools": {
"check_llm_compatibility": {}
}
}check_llm_compatibility 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) Checks if a specific LLM model can run on this machine. Returns optimal quantization and estimated tokens per second. 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 check_llm_compatibility: 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.
check_llm_compatibility 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 check_llm_compatibility 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 check_llm_compatibility. 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.
check_llm_compatibility 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.