get_pending_devices

List devices that have tried to connect but are not yet configured.

Server Syncthing MCP Server zaphodsdad/syncthing-mcp
Category Read
Risk class Low
Parameters 00 required

What get_pending_devices does on Syncthing MCP Server

AI agents call get_pending_devices 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.

Why get_pending_devices needs a policy

This tool performs a passive information retrieval operation—it lists pending device connection requests. There are no side effects, no data modifications, no code execution, and no destructive or financial operations. It is purely a query/fetch operation, fitting the 'Read' category with low severity due to minimal blast radius if misused (only information disclosure about pending connections).

From the tool's definition Tool name 'get_pending_devices' and description 'List devices that have tried to connect but are not yet configured' indicate a read-only query operation that retrieves connection status information without modifying any state.

Questions about get_pending_devices

What does the get_pending_devices tool do? +

List devices that have tried to connect but are not yet configured. It is categorised as a Read tool in the Syncthing MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pending_devices? +

Register the Syncthing MCP Server MCP server in PolicyLayer and add a rule for get_pending_devices: 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.

What risk level is get_pending_devices? +

get_pending_devices is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pending_devices? +

Yes. Add a rate_limit block to the get_pending_devices 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.

How do I block get_pending_devices completely? +

Set action: deny in the PolicyLayer policy for get_pending_devices. 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.

What MCP server provides get_pending_devices? +

get_pending_devices 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.