Enable or disable a file-sharing protocol. [control]
AI agents invoke set_file_service to trigger actions in Synology 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.
Enabling or disabling a file-sharing protocol (e.g., SMB, NFS, AFP) triggers a system-level service state change on the NAS. This is not a simple write/read operation — it executes a control action that affects network accessibility of the device. Misuse could expose the NAS to unauthorized access (enabling insecure protocols) or cause a denial of service (disabling needed protocols).
From the tool's definition 'Enable or disable a file-sharing protocol' and '[control]' tag indicate toggling network services on/off, which is an external operational change with broad network-access implications.
Attacks that exploit this kind of access
Enable or disable a file-sharing protocol. [control]. It is categorised as a Execute tool in the Synology MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Synology MCP Server MCP server in PolicyLayer and add a rule for set_file_service: 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 Synology MCP Server. Nothing to install.
set_file_service 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 set_file_service 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 set_file_service. 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.
set_file_service is provided by the Synology MCP Server MCP server (rafalr100/synology-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 →