check_freshrss
Check FreshRSS feed aggregator availability. FreshRSS has no dedicated health endpoint; checks if the main page or /i/ returns HTTP 200.
This record as markdown: /tools/aaronckj-mcp-nettools/check-freshrss.md
What check_freshrss does on Mcp Nettools
AI agents call check_freshrss 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_freshrss is rated Low
This tool retrieves the HTTP status of a web endpoint to determine availability/health. It is a pure read operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—worst case would be repeated health check requests causing minor load on a target service.
From the tool's definition Tool performs HTTP status checks against FreshRSS endpoints (main page or /i/); returns availability status without modifying any data or triggering side effects.
Attacks that exploit this kind of access
The rule that runs check_freshrss 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_freshrss, this is the rule to start with:
check_freshrss 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_freshrss call is checked against it from then on.
Questions about check_freshrss
Check FreshRSS feed aggregator availability. FreshRSS has no dedicated health endpoint; checks if the main page or /i/ returns HTTP 200. 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_freshrss: 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_freshrss 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_freshrss 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_freshrss. 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_freshrss 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