List currently active connections to the NAS (who, from where, which protocol).
AI agents call get_active_connections to retrieve information from Synology MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about active connections to the NAS without creating, modifying, deleting, or executing any operations. It is purely informational and has no destructive or financial impact.
From the tool's definition Tool name and description explicitly indicate 'List currently active connections' — a query operation that retrieves connection metadata (who, from where, which protocol) with no modification or side effects.
Attacks that exploit this kind of access
List currently active connections to the NAS (who, from where, which protocol). It is categorised as a Read tool in the Synology MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Synology MCP Server MCP server in PolicyLayer and add a rule for get_active_connections: 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.
get_active_connections 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 get_active_connections 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 get_active_connections. 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.
get_active_connections 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 →