AI agents call check_installation to retrieve information from Unsloth MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic check to verify installation status. It retrieves information about the system state (whether Unsloth is installed) with no side effects, no data modification, no code execution, and no irreversible actions. This is a pure Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'check_installation' and description 'Check if Unsloth is properly installed' indicate a status check that queries the system state without modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access check_installation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unsloth MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_installation:
{
"version": "1",
"default": "deny",
"tools": {
"check_installation": {}
}
}check_installation 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.
Check if Unsloth is properly installed. It is categorised as a Read tool in the Unsloth MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unsloth MCP Server MCP server in PolicyLayer and add a rule for check_installation: 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 Unsloth MCP Server. Nothing to install.
check_installation 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_installation 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_installation. 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_installation is provided by the Unsloth MCP Server MCP server (ototao/unsloth-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Unsloth 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.
6 Unsloth MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.