check_penpot

Check Penpot open-source design tool health via GET /api/rpc/command/get-profile. 401 = running (auth required). Default port 9001.

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

WHAT IT DOES

What check_penpot does on Mcp Nettools

AI agents call check_penpot 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_penpot is rated Low

This tool retrieves service health information without side effects. GET requests are non-modifying read operations. The low severity reflects that probing a service's health endpoint poses minimal risk even if misused by an agent—it cannot corrupt, delete, or modify data, nor trigger external operations with unintended consequences. Confidence is high because the GET method and health-check nature are explicit.

From the tool's definition Tool performs a GET request to /api/rpc/command/get-profile to check service health. No data is modified, deleted, or financial operations are triggered.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_penpot Allowed

check_penpot 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_penpot": {}
  }
}

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

FAQ

Questions about check_penpot

What does the check_penpot tool do? +

Check Penpot open-source design tool health via GET /api/rpc/command/get-profile. 401 = running (auth required). Default port 9001. 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_penpot? +

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

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

Can I rate-limit check_penpot? +

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

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

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