Request the server to exit so a process manager can restart it (SSE only).
AI agents invoke restart_server to trigger actions in Srclight. 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.
This tool triggers restart of the srclight server itself—an external operation that causes the service to stop and restart. While not destructive (data is preserved) and not immediately dangerous if misused in isolation, it can disrupt availability and workflow. Categorized as Execute rather than Destructive because the action is reversible (restart completes and service resumes) and doesn't delete or corrupt data.
From the tool's definition Tool explicitly requests server exit/restart via process manager. Description states 'exit so a process manager can restart it', indicating execution of a server lifecycle operation with external side effects.
Documented attack patterns abuse exactly the kind of access restart_server gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Srclight, and nothing reaches the server without passing your rules. This is the rule we recommend for restart_server:
{
"version": "1",
"default": "deny",
"tools": {
"restart_server": {
"limits": [
{
"counter": "restart_server_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}restart_server 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.
Free to start. No card required.
Request the server to exit so a process manager can restart it (SSE only). It is categorised as a Execute tool in the Srclight MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Srclight MCP server in PolicyLayer and add a rule for restart_server: 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 Srclight. Nothing to install.
restart_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the restart_server 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.
Set action: deny in the PolicyLayer policy for restart_server. 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.
restart_server is provided by the Srclight MCP server (srclight/srclight). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Srclight tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Srclight tools catalogued and risk-classified — across an index of 42,500+ MCP servers.