Get connection status for all devices including bandwidth and addresses.
AI agents call get_connections to retrieve information from Syncthing 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 retrieves connection status information (bandwidth, addresses) for monitoring purposes. It performs no writes, deletes, executions, or financial operations. The read-only nature and informational scope make this a low-severity Read operation.
From the tool's definition Tool name 'get_connections' and description 'Get connection status for all devices including bandwidth and addresses' indicate retrieval of connection metadata without modification, deletion, or side effects.
Attacks that exploit this kind of access
Get connection status for all devices including bandwidth and addresses. It is categorised as a Read tool in the Syncthing MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Syncthing MCP Server MCP server in PolicyLayer and add a rule for get_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 Syncthing MCP Server. Nothing to install.
get_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_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_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_connections is provided by the Syncthing MCP Server MCP server (zaphodsdad/syncthing-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 →