close_ui

Stop the Project Guardian Web UI server if running. Use after start_ui or to free port 3000.

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server

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/1999azzar-project-guardian-mcp-server/close-ui.md

WHAT IT DOES

What close_ui does on Project Guardian MCP

AI agents invoke close_ui to trigger actions in Project Guardian MCP. 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.

RISK

Why close_ui is rated High

Terminates a running server process, an external operation with system-level effects.

From the tool's definition Stop the Project Guardian Web UI server if running

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs close_ui safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_ui, this is the rule to start with:

close_ui Rate-limited

close_ui 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": {
    "close_ui": {
      "limits": [
        {
          "counter": "close_ui_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Project Guardian MCP, apply this rule, and every close_ui call is checked against it from then on.

FAQ

Questions about close_ui

What does the close_ui tool do? +

Stop the Project Guardian Web UI server if running. Use after start_ui or to free port 3000. It is categorised as a Execute tool in the Project Guardian MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on close_ui? +

Register the Project Guardian MCP server in PolicyLayer and add a rule for close_ui: 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 Project Guardian MCP. Nothing to install.

What risk level is close_ui? +

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

Can I rate-limit close_ui? +

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

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

close_ui is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Project Guardian, and thousands of servers like it.

This server

All 38 Project Guardian tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →