Repair an MCP server by uninstalling and reinstalling it. Requires the keyword to find the server and the original installation URL.
AI agents invoke repair_mcp_server to trigger actions in Mcp Easy Installer. 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.
The repair operation performs a multi-step process: it first uninstalls an MCP server (irreversible removal) and then reinstalls it (code execution/installation). The most severe applicable category is Execute, as it triggers external installation operations and runs setup processes.
From the tool's definition 'Repair an MCP server by uninstalling and reinstalling it' — involves uninstalling (destructive) and reinstalling (execute/write) as a combined automated operation
Documented attack patterns abuse exactly the kind of access repair_mcp_server gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Easy Installer, and nothing reaches the server without passing your rules. This is the rule we recommend for repair_mcp_server:
{
"version": "1",
"default": "deny",
"tools": {
"repair_mcp_server": {
"limits": [
{
"counter": "repair_mcp_server_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}repair_mcp_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.
Repair an MCP server by uninstalling and reinstalling it. Requires the keyword to find the server and the original installation URL. It is categorised as a Execute tool in the Mcp Easy Installer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Easy Installer MCP server in PolicyLayer and add a rule for repair_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 Mcp Easy Installer. Nothing to install.
repair_mcp_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 repair_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.
Set action: deny in the PolicyLayer policy for repair_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.
repair_mcp_server is provided by the Mcp Easy Installer MCP server (onigetoc/mcp-easy-installer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Easy Installer, 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.
4 Mcp Easy Installer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.