check_shiori
Check Shiori bookmark manager reachability via GET /. Returns 200 or 302 (redirect to login) when service is up. Default port 8080.
This record as markdown: /tools/aaronckj-mcp-nettools/check-shiori.md
What check_shiori does on Mcp Nettools
AI agents call check_shiori 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_shiori is rated Low
This is a basic health check operation that queries whether a service is reachable. It uses HTTP GET, which is a read-only operation. There is no data modification, command execution, or deletion involved. The blast radius of misuse is minimal—an attacker could only discover that a service exists or is running, which is low-impact reconnaissance information.
From the tool's definition Tool description states it performs a GET request to check reachability and returns HTTP status codes (200 or 302). The operation is purely diagnostic—it only reads the service status without modifying any data, executing commands, or triggering side effects.
Attacks that exploit this kind of access
The rule that runs check_shiori 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_shiori, this is the rule to start with:
check_shiori 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_shiori call is checked against it from then on.
Questions about check_shiori
Check Shiori bookmark manager reachability via GET /. Returns 200 or 302 (redirect to login) when service is up. Default port 8080. 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_shiori: 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_shiori 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_shiori 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_shiori. 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_shiori 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