check_stirling_pdf

Check Stirling-PDF tools server health via GET /api/v1/info. Returns healthy state and version.

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-stirling-pdf.md

WHAT IT DOES

What check_stirling_pdf does on Mcp Nettools

AI agents call check_stirling_pdf 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.

RISK

Why check_stirling_pdf is rated Low

This tool performs a simple HTTP GET request to a health check endpoint and retrieves server status and version information. No data is modified, created, deleted, or executed. It is a passive monitoring/diagnostic operation typical of health check probes. The retrieval of health status and version information constitutes a Read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool description states it 'Check[s] Stirling-PDF tools server health via GET /api/v1/info. Returns healthy state and version.' The HTTP method is GET and the action is retrieving read-only health/status information with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_stirling_pdf 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_stirling_pdf, this is the rule to start with:

check_stirling_pdf Allowed

check_stirling_pdf is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_stirling_pdf": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_stirling_pdf call is checked against it from then on.

FAQ

Questions about check_stirling_pdf

What does the check_stirling_pdf tool do? +

Check Stirling-PDF tools server health via GET /api/v1/info. Returns healthy state and version. 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_stirling_pdf? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_stirling_pdf: 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_stirling_pdf? +

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

Can I rate-limit check_stirling_pdf? +

Yes. Add a rate_limit block to the check_stirling_pdf 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_stirling_pdf completely? +

Set action: deny in the PolicyLayer policy for check_stirling_pdf. 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_stirling_pdf? +

check_stirling_pdf 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.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →