stirling_status
Check whether the Stirling PDF container is reachable. Returns the HTTP status of the home page and the configured URL.
This record as markdown: /tools/kh0pper-crow/stirling-status.md
What stirling_status does on Crow
AI agents call stirling_status to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stirling_status is rated Low
This is a simple health check or monitoring tool that retrieves status information about a service. It queries and returns data without modifying, executing code, deleting, or committing financial transactions. The action is passive and informational in nature, fitting clearly into the Read category with low severity since misuse would only expose service availability metadata.
From the tool's definition Tool performs a status check by querying the HTTP status of a remote service endpoint. The description explicitly states it 'Check[s] whether the Stirling PDF container is reachable' and 'Returns the HTTP status', which are read-only diagnostic operations…
Attacks that exploit this kind of access
The rule that runs stirling_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stirling_status, this is the rule to start with:
stirling_status 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 Crow, apply this rule, and every stirling_status call is checked against it from then on.
Questions about stirling_status
Check whether the Stirling PDF container is reachable. Returns the HTTP status of the home page and the configured URL. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for stirling_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 Crow. Nothing to install.
stirling_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 stirling_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 stirling_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.
stirling_status is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue