Check whether the Stirling PDF container is reachable. Returns the HTTP status of the home page and the configured URL.
AI agents call stirling_status to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple health check or status query against a service endpoint. It retrieves information (HTTP status code) about the Stirling PDF container's availability and configuration. No data is created, modified, deleted, or executed—only observed. This is a classic Read category operation with minimal blast radius if misused by an AI agent, as it only reveals service status information.
From the tool's definition Tool description states it 'Check[s] whether the Stirling PDF container is reachable' and 'Returns the HTTP status'. These are read-only query operations that retrieve status information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access stirling_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for stirling_status:
{
"version": "1",
"default": "deny",
"tools": {
"stirling_status": {}
}
}stirling_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.