port_check
Check if a network port is open on a host.
This record as markdown: /tools/io-github-scotia1973-bot-api-hub/port-check.md
What port_check does on GadgetHumans API Hub
AI agents call port_check to retrieve information from GadgetHumans API Hub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why port_check is rated Low
This tool performs reconnaissance by testing port availability, which is a read-only diagnostic operation. While port scanning can inform malicious activity, the tool itself does not execute commands, modify data, or trigger external changes. It falls clearly into the Read category as it only queries and reports network state.
From the tool's definition Tool description states 'Check if a network port is open on a host' — a pure query operation that retrieves network status information with no side effects, modification, or code execution.
Attacks that exploit this kind of access
The rule that runs port_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GadgetHumans API Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For port_check, this is the rule to start with:
port_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GadgetHumans API Hub, apply this rule, and every port_check call is checked against it from then on.
Questions about port_check
Check if a network port is open on a host. It is categorised as a Read tool in the GadgetHumans API Hub MCP Server, which means it retrieves data without modifying state.
Register the GadgetHumans API Hub MCP server in PolicyLayer and add a rule for port_check: 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 GadgetHumans API Hub. Nothing to install.
port_check 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_check 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_check. 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_check is provided by the GadgetHumans API Hub MCP server (pypi:gadgethumans-api-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GadgetHumans API Hub, and thousands of servers like it.
This server
Across the catalogue