AI agents call ftp_analyze_workspace to retrieve information from Ftp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read tool—it queries remote directory structures and accesses manifest files to understand codebase architecture. While introspection of a codebase could reveal sensitive information about dependencies and infrastructure (medium severity), the operation itself is non-destructive and reversible.
From the tool's definition Tool performs introspection and reads dependency manifests without modifying data. The description explicitly states 'identify technical environments' and 'read dependency manifests', which are query/retrieval operations.
Attacks that exploit this kind of access
Introspect the remote directory to identify technical environments (e.g., Node.js, PHP, Python) and read dependency manifests. Use this to gain architectural context of a new codebase. It is categorised as a Read tool in the Ftp MCP Server, which means it retrieves data without modifying state.
Register the Ftp MCP server in PolicyLayer and add a rule for ftp_analyze_workspace: 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 Ftp. Nothing to install.
ftp_analyze_workspace 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 ftp_analyze_workspace 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 ftp_analyze_workspace. 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.
ftp_analyze_workspace is provided by the Ftp MCP server (kynlos/ftp-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 →