dev_request_restart · RPG Ledger MCP Server MCP

WHAT IT DOES

What dev_request_restart does on RPG Ledger MCP Server

AI agents invoke dev_request_restart to trigger actions in RPG Ledger MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why dev_request_restart needs a policy

This tool executes an external operation (service restart) whose effects depend on arguments and cannot be trivially rolled back. Restarting services disrupts ongoing operations and affects system state. While not permanently destructive, it has significant blast radius if triggered inappropriately by an AI agent.

From the tool's definition Tool name 'dev_request_restart' and description (Polish: 'Report/submit a request for stack/services restart') indicates triggering a restart of infrastructure services/stack.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dev_request_restart Rate-limited

dev_request_restart stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dev_request_restart": {
      "limits": [
        {
          "counter": "dev_request_restart_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RPG Ledger MCP Server, so you can run agents against it safely.

FAQ

Questions about dev_request_restart

What does the dev_request_restart tool do? +

Zgłoś prośbę o restart stacka / serwisów. It is categorised as a Execute tool in the RPG Ledger MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dev_request_restart? +

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

What risk level is dev_request_restart? +

dev_request_restart is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dev_request_restart? +

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

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

dev_request_restart is provided by the RPG Ledger MCP Server MCP server (sepa79/rpg-ledger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.