check_shiori

Check Shiori bookmark manager reachability via GET /. Returns 200 or 302 (redirect to login) when service is up. Default port 8080.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about check_shiori

What does the check_shiori tool do? +

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.

How do I enforce a policy on check_shiori? +

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.

What risk level is check_shiori? +

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

Can I rate-limit check_shiori? +

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.

How do I block check_shiori completely? +

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.

What MCP server provides check_shiori? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Nettools's. Pull the full record:

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.