Update FTP service configuration. All fields are optional — only provide the ones you want to change. Restart the FTP service after changes.
AI agents use ftp_config_update to create or update resources in Truenas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas environment.
This tool modifies FTP service configuration settings, which is a Write operation. It is reversible (config can be changed again) and does not delete data or execute arbitrary code. Severity is medium because misconfiguration of FTP services could expose systems or data if settings like authentication or access controls are altered maliciously, but the changes themselves are not destructive and can be corrected.
From the tool's definition Tool name 'ftp_config_update' and description states it 'Update[s] FTP service configuration' and 'Restart the FTP service after changes'. These are reversible modifications to service settings.
Documented attack patterns abuse exactly the kind of access ftp_config_update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for ftp_config_update:
{
"version": "1",
"default": "deny",
"tools": {
"ftp_config_update": {
"limits": [
{
"counter": "ftp_config_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ftp_config_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update FTP service configuration. All fields are optional — only provide the ones you want to change. Restart the FTP service after changes. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Truenas MCP server in PolicyLayer and add a rule for ftp_config_update: 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 Truenas. Nothing to install.
ftp_config_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ftp_config_update 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_config_update. 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_config_update is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.