This record as markdown: /tools/io-tinyfn-tinyfn/port-info.md
What port_info does on TinyFn
AI agents call port_info to retrieve information from TinyFn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
port | integer | Yes | Port number |
Parameters from the server's own tool schema.
Why port_info is rated Low
This tool retrieves static information about a port number (such as its standard protocol, service name, or other metadata). It is a read-only operation that does not modify, execute, or delete anything. The low severity reflects that port information is typically public and non-sensitive data, and misuse would have minimal blast radius.
From the tool's definition Tool name 'port_info' and description 'Get information about a port number' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs port_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For port_info, this is the rule to start with:
port_info 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 TinyFn, apply this rule, and every port_info call is checked against it from then on.
Questions about port_info
Get information about a port number. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
port_info accepts 1 parameter: port. Required: port. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for port_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 TinyFn. Nothing to install.
port_info 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_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.
Set action: deny in the PolicyLayer policy for port_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.
port_info is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue