Low Risk

check_tool_health

Perform comprehensive health check on all tools.

How to control check_tool_health ↓

What check_tool_health does on Inkscape

AI agents call check_tool_health to retrieve information from Inkscape without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why check_tool_health needs a policy

Health checks are non-destructive, read-only operations that query the state of tools and systems. They do not create, modify, delete data, execute arbitrary commands, or trigger external side effects. This is purely informational/diagnostic, matching the Read category.

From the tool's definition The tool name 'check_tool_health' and description 'Perform comprehensive health check on all tools' indicate a diagnostic/monitoring operation that retrieves system status information without modifying or executing external operations.

Documented attack patterns abuse exactly the kind of access check_tool_health gives an agent:

How to control check_tool_health

PolicyLayer is an MCP gateway — it sits between your AI agents and Inkscape, and nothing reaches the server without passing your rules. This is the rule we recommend for check_tool_health:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_tool_health": {}
  }
}

check_tool_health is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Inkscape — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about check_tool_health

What does the check_tool_health tool do? +

Perform comprehensive health check on all tools. It is categorised as a Read tool in the Inkscape MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_tool_health? +

Register the Inkscape MCP server in PolicyLayer and add a rule for check_tool_health: 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 Inkscape. Nothing to install.

What risk level is check_tool_health? +

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

Can I rate-limit check_tool_health? +

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

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

check_tool_health is provided by the Inkscape MCP server (sandraschi/inkscape-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Inkscape tool call.

Start from Inkscape, 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.

58 Inkscape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.