ssh_upload_and_extract
AI agents invoke ssh_upload_and_extract to trigger actions in SSH MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool likely uploads an archive to a remote server and extracts it, combining a Write action (upload) with an Execute action (extraction). Archive extraction can overwrite existing files and execute path traversal attacks, making it potentially destructive. The description is empty, so confidence is reduced, but the server context and sibling tools strongly suggest this behavior.
From the tool's definition Tool name 'ssh_upload_and_extract' on a server described as supporting 'recursive directory uploads, archive extraction, and direct file creation from text content' via SSH.
Attacks that exploit this kind of access
ssh_upload_and_extract. It is categorised as a Execute tool in the SSH MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for ssh_upload_and_extract: 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 SSH MCP Server. Nothing to install.
ssh_upload_and_extract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ssh_upload_and_extract 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 ssh_upload_and_extract. 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.
ssh_upload_and_extract is provided by the SSH MCP Server MCP server (mcpol-studio/code-to-server-ssh-mcp). 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 →