TCP and/or UDP endpoints with owning process. protocol: tcp, udp, both, all.
AI agents call get_network_connections to retrieve information from Procmon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing network connection information (read-only access to system state), similar to netstat or Get-NetTCPConnection. It has no side effects, does not execute code, create/modify data, or delete anything.
From the tool's definition Tool retrieves 'TCP and/or UDP endpoints with owning process' without modifying or executing anything. The description indicates data retrieval of network connection state only.
Documented attack patterns abuse exactly the kind of access get_network_connections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Procmon, and nothing reaches the server without passing your rules. This is the rule we recommend for get_network_connections:
{
"version": "1",
"default": "deny",
"tools": {
"get_network_connections": {}
}
} get_network_connections 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.
TCP and/or UDP endpoints with owning process. protocol: tcp, udp, both, all. It is categorised as a Read tool in the Procmon MCP Server, which means it retrieves data without modifying state.
Register the Procmon MCP server in PolicyLayer and add a rule for get_network_connections: 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.
get_network_connections 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_network_connections 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_network_connections. 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_network_connections 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.
Deterministic rules across all 18 Procmon tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Procmon tools catalogued and risk-classified — across an index of 42,500+ MCP servers.