Check which REMnux analysis tools are installed and available. Returns a summary of installed vs missing tools across all file type categories.
AI agents call check_tools to retrieve information from REMnux 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 and queries the state of installed tools on the REMnux system. It performs no data modification, execution of analysis, deletion, or financial operations. It is a simple informational read operation that returns tool availability status. The low severity reflects minimal risk even if misused by an AI agent—querying tool availability poses no blast radius.
From the tool's definition Tool name is 'check_tools' and description states it 'Check[s] which REMnux analysis tools are installed and available' and 'Returns a summary of installed vs missing tools'. This is purely a query/inventory operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access check_tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and REMnux MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_tools:
{
"version": "1",
"default": "deny",
"tools": {
"check_tools": {}
}
}check_tools 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 which REMnux analysis tools are installed and available. Returns a summary of installed vs missing tools across all file type categories. It is categorised as a Read tool in the REMnux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the REMnux MCP Server MCP server in PolicyLayer and add a rule for check_tools: 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 REMnux MCP Server. Nothing to install.
check_tools 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_tools 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_tools. 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_tools is provided by the REMnux MCP Server MCP server (remnux/remnux-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 REMnux MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 REMnux MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.