AI agents call get_system_info to retrieve information from LuzzyTool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports system metadata without side effects. It queries read-only system properties and statistics. This is a standard informational operation with no capacity to modify state, execute code, or create any impact beyond reading publicly accessible system information.
From the tool's definition Tool name 'get_system_info' and description describing retrieval of system environment information (operating system, kernel version, CPU architecture, Python version, memory usage, etc.) with no capability to modify or execute operations.
Attacks that exploit this kind of access
【按需调用】获取当前系统环境信息（操作系统、内核版本、CPU 架构、Python 版本、内存使用率等）。. It is categorised as a Read tool in the LuzzyTool MCP Server, which means it retrieves data without modifying state.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for get_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 LuzzyTool. Nothing to install.
get_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 get_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 get_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.
get_system_info is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →