Get configured DDNS records (hostname, external IP, last update, status).
AI agents call get_ddns_status 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 only queries and retrieves DDNS configuration data and status—it performs no writes, deletes, code execution, or financial operations. The action is purely informational with no side effects. Low severity because exposure of DDNS hostnames and external IP addresses has limited direct impact, though it could inform further reconnaissance in a broader attack.
From the tool's definition Tool name 'get_ddns_status' and description 'Get configured DDNS records (hostname, external IP, last update, status)' indicate retrieval of existing configuration and status information with no modification.
Attacks that exploit this kind of access
Get configured DDNS records (hostname, external IP, last update, status). 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_ddns_status: 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_ddns_status 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_ddns_status 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_ddns_status. 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_ddns_status 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 →