New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

libi.restart_mcp_server

Restart a specific bundled MCP server. Use after fixing an issue diagnose_mcp surfaced (e.g. installed a missing binary, set an API key). Returns immediately; the restart happens server-side. Per current claude-agent-acp limitations, all bundled MCPs restart together — the tool tells you to ask t...

SERVERLibi SOURCENagellabs/libi
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/libi/libi.restart-mcp-server.md

What libi.restart_mcp_server does on Libi

AI agents invoke libi.restart_mcp_server to trigger actions in Libi. 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 libi.restart_mcp_server is rated High

Restarts MCP servers with side effects affecting system state and all bundled services simultaneously.

From the tool's definition Restart a specific bundled MCP server; all bundled MCPs restart together

Questions about libi.restart_mcp_server

What does the libi.restart_mcp_server tool do? +

Restart a specific bundled MCP server. Use after fixing an issue diagnose_mcp surfaced (e.g. installed a missing binary, set an API key). Returns immediately; the restart happens server-side. Per current claude-agent-acp limitations, all bundled MCPs restart together — the tool tells you to ask the user to open a new chat (or re-send) so the new session picks up the rebuilt MCP list. It is categorised as a Execute tool in the Libi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on libi.restart_mcp_server? +

Register the Libi MCP server in PolicyLayer and add a rule for libi.restart_mcp_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 Libi. Nothing to install.

What risk level is libi.restart_mcp_server? +

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

Can I rate-limit libi.restart_mcp_server? +

Yes. Add a rate_limit block to the libi.restart_mcp_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.

How do I block libi.restart_mcp_server completely? +

Set action: deny in the PolicyLayer policy for libi.restart_mcp_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.

What MCP server provides libi.restart_mcp_server? +

libi.restart_mcp_server is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Libi, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Libi's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.