Get comprehensive system information, server details, available tool categories, and resource usage. Example: system information, tool categories, installation guide
AI agents call system_info to retrieve information from IT Tools 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 read-only queries of system state and metadata. It returns information about the system, available tools, and resource usage without modifying any data, executing code, or triggering external operations.
From the tool's definition Tool retrieves 'comprehensive system information, server details, available tool categories, and resource usage' with no mention of modification, deletion, or execution capabilities. The word 'Get' indicates data retrieval only.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access system_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IT Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for system_info:
{
"version": "1",
"default": "deny",
"tools": {
"system_info": {}
}
} system_info 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.
Get comprehensive system information, server details, available tool categories, and resource usage. Example: system information, tool categories, installation guide. It is categorised as a Read tool in the IT Tools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IT Tools MCP Server MCP server in PolicyLayer and add a rule for system_info: 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 IT Tools MCP Server. Nothing to install.
system_info 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 system_info 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 system_info. 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.
system_info is provided by the IT Tools MCP Server MCP server (wrenchpilot/it-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from IT Tools 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.
119 IT Tools MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.