New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_system_info

A read tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/get-system-info.md

What get_system_info does on Allcanuse

AI agents call get_system_info to retrieve information from Allcanuse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_system_info is rated Low

The tool name 'get_system_info' follows read-operation naming conventions (get/retrieve pattern). System information queries are typically informational and do not modify, delete, or execute operations. Even on a server with extensive system management capabilities, a 'get_system_info' call should be confined to querying OS details, hardware specs, or configuration—all read-only operations.

From the tool's definition Tool name 'get_system_info' indicates retrieval of system information with no side effects. Description is empty but the name strongly suggests a read-only query operation.

Questions about get_system_info

What does the get_system_info tool do? +

get_system_info is a read tool on the Allcanuse MCP server. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_system_info? +

Register the Allcanuse 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 Allcanuse. Nothing to install.

What risk level is get_system_info? +

get_system_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_system_info? +

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.

How do I block get_system_info completely? +

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.

What MCP server provides get_system_info? +

get_system_info is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Allcanuse, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Allcanuse's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.