check_planka

Check Planka kanban project management board health via GET /api/health or root path. 200 or 401 = healthy. Default port 1337.

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

WHAT IT DOES

What check_planka does on Mcp Nettools

AI agents call check_planka 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_planka is rated Low

This is a read-only diagnostic operation that queries the health status of a Planka service. It retrieves information about system status without side effects. The tool only checks connectivity and health status of a web service on port 1337, which is consistent with the server's purpose of network diagnostics. No write, execute, destructive, or financial operations are performed.

From the tool's definition Tool performs a GET request to check health endpoint (/api/health or root path). Returns health status based on HTTP response codes (200 or 401). No data modification, deletion, or external state changes occur.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_planka Allowed

check_planka 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_planka": {}
  }
}

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

FAQ

Questions about check_planka

What does the check_planka tool do? +

Check Planka kanban project management board health via GET /api/health or root path. 200 or 401 = healthy. Default port 1337. 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_planka? +

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

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

Can I rate-limit check_planka? +

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

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

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