Low Risk

get_server_status

Get comprehensive server status and health information.

How to control get_server_status ↓

What get_server_status does on Inkscape

AI agents call get_server_status 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 get_server_status needs a policy

This tool retrieves status information about the Inkscape MCP server without modifying, executing, or affecting any graphics, files, or external systems. It is a read-only diagnostic query, making it the safest category with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_server_status' and description 'Get comprehensive server status and health information' indicate a query/retrieval operation with no side effects.

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

How to control get_server_status

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 get_server_status:

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

get_server_status 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 get_server_status

What does the get_server_status tool do? +

Get comprehensive server status and health information. 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 get_server_status? +

Register the Inkscape MCP server in PolicyLayer and add a rule for get_server_status: 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 get_server_status? +

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

Can I rate-limit get_server_status? +

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

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

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