get_system_info

OS build, architecture, hostname, SecurityCenter2 AV products, PowerShell version.

SERVERProcmon SOURCE0xhackerfren/procmon-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/0xhackerfren-procmon-mcp/get-system-info.md

WHAT IT DOES

What get_system_info does on Procmon

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

RISK

Why get_system_info is rated Low

This tool only gathers and returns information about the system state. It performs queries without creating, modifying, deleting, executing code, or committing any financial actions. The data returned (OS details, AV status, versions) are static system properties accessed via standard read operations.

From the tool's definition Tool retrieves system metadata: 'OS build, architecture, hostname, SecurityCenter2 AV products, PowerShell version.' All are read-only queries with no side effects or modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_system_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Procmon, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_system_info, this is the rule to start with:

get_system_info Allowed

get_system_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_system_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Procmon, apply this rule, and every get_system_info call is checked against it from then on.

FAQ

Questions about get_system_info

What does the get_system_info tool do? +

OS build, architecture, hostname, SecurityCenter2 AV products, PowerShell version. It is categorised as a Read tool in the Procmon MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_system_info? +

Register the Procmon 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 Procmon. 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 Procmon MCP server (0xhackerfren/procmon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Procmon, and thousands of servers like it.

This server

All 18 Procmon tools →

Across the catalogue

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →