Get ports that are listening on the system.
AI agents call get_listening_ports to retrieve information from Linux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about network listening ports without modifying, executing, or deleting anything. It is a passive diagnostic query analogous to running 'netstat -l' or 'ss -l'. While port information could theoretically inform reconnaissance, the tool itself performs no actions and has minimal blast radius if invoked by an AI agent.
From the tool's definition Tool name 'get_listening_ports' and description 'Get ports that are listening on the system' indicate a read-only query operation. The server is explicitly described as 'read-only Linux system diagnostics' with no side effects.
Attacks that exploit this kind of access
Get ports that are listening on the system. It is categorised as a Read tool in the Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linux MCP Server MCP server in PolicyLayer and add a rule for get_listening_ports: 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 Linux MCP Server. Nothing to install.
get_listening_ports 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_listening_ports 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_listening_ports. 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_listening_ports is provided by the Linux MCP Server MCP server (narmaku/linux-mcp-server-archived). 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 →