check_changedetection
Check changedetection.io web change monitoring server health via GET /api/v1/systeminfo. Returns version. Default port 5000.
This record as markdown: /tools/aaronckj-mcp-nettools/check-changedetection.md
What check_changedetection does on Mcp Nettools
AI agents call check_changedetection to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_changedetection is rated Low
This tool queries server metadata and health status without modifying, executing, or deleting anything. It is a pure information retrieval operation (Read category). The blast radius is minimal—an attacker could learn the server version, which poses a low severity risk since it only exposes informational data that could inform further reconnaissance but causes no direct harm.
From the tool's definition Tool performs a GET request to retrieve system information (version) from a changedetection.io server. The description explicitly states 'Returns version' and uses GET /api/v1/systeminfo, which is a read-only health check operation with no side effects.
Attacks that exploit this kind of access
The rule that runs check_changedetection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_changedetection, this is the rule to start with:
check_changedetection is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_changedetection call is checked against it from then on.
Questions about check_changedetection
Check changedetection.io web change monitoring server health via GET /api/v1/systeminfo. Returns version. Default port 5000. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_changedetection: 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 Mcp Nettools. Nothing to install.
check_changedetection 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 check_changedetection 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 check_changedetection. 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.
check_changedetection is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue