AI agents call getFileTransferStatus to retrieve information from Mcp Ssh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of an existing file transfer operation. It performs no side effects, creates no new state, executes no commands, and modifies no data. The 'get' verb and 'status' operation are characteristic of Read category tools. While the server overall enables potentially sensitive SSH operations, this specific tool is limited to passive information retrieval about file transfers.
From the tool's definition Tool name 'getFileTransferStatus' and description 'Gets the status of a specific file transfer' indicate a read-only operation that retrieves state information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access getFileTransferStatus gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ssh, and nothing reaches the server without passing your rules. This is the rule we recommend for getFileTransferStatus:
{
"version": "1",
"default": "deny",
"tools": {
"getFileTransferStatus": {}
}
}getFileTransferStatus 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.
Gets the status of a specific file transfer. It is categorised as a Read tool in the Mcp Ssh MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ssh MCP server in PolicyLayer and add a rule for getFileTransferStatus: 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 Mcp Ssh. Nothing to install.
getFileTransferStatus 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 getFileTransferStatus 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 getFileTransferStatus. 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.
getFileTransferStatus is provided by the Mcp Ssh MCP server (shuakami/mcp-ssh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Mcp Ssh tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
23 Mcp Ssh tools catalogued and risk-classified — across an index of 42,500+ MCP servers.