AI agents call port_status to retrieve information from PSKit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
port_status performs system introspection to enumerate listening TCP ports and their owning processes. This is a read-only operation that gathers information about the current system state without modifying, executing code, deleting, or moving money. While it reveals system architecture details that could inform an attacker's reconnaissance, the tool itself performs no harmful actions.
From the tool's definition Tool retrieves port and process information: 'Check which TCP ports are listening and which processes own them.' This is a query/inspection operation with no side effects.
Attacks that exploit this kind of access
Check which TCP ports are listening and which processes own them. It is categorised as a Read tool in the PSKit MCP Server, which means it retrieves data without modifying state.
Register the PSKit MCP server in PolicyLayer and add a rule for port_status: 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 PSKit. Nothing to install.
port_status 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 port_status 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 port_status. 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.
port_status is provided by the PSKit MCP server (nickalus12/pskit). 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 →