check_ghost

Check Ghost blog platform health via GET /ghost/api/admin/site/. Returns version and site title. Default port 2368.

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-ghost.md

WHAT IT DOES

What check_ghost does on Mcp Nettools

AI agents call check_ghost 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_ghost is rated Low

This tool queries a Ghost blog API endpoint to retrieve diagnostic information (version, site title) without any side effects. It is a passive information retrieval operation that does not create, modify, delete, or execute anything. The blast radius of misuse is minimal—an attacker would only gain visibility into Ghost blog metadata if the admin API is exposed.

From the tool's definition Tool description indicates it performs a GET request to retrieve Ghost blog platform health information, returning version and site title.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_ghost Allowed

check_ghost 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_ghost": {}
  }
}

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_ghost call is checked against it from then on.

FAQ

Questions about check_ghost

What does the check_ghost tool do? +

Check Ghost blog platform health via GET /ghost/api/admin/site/. Returns version and site title. Default port 2368. 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_ghost? +

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

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

Can I rate-limit check_ghost? +

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

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

check_ghost 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 →