start_ui
Start the Project Guardian Web UI server on demand. Automatically searches for a free port and returns the local HTTP URL.
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/start-ui.md
What start_ui does on Project Guardian MCP
AI agents invoke start_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.
Why start_ui is rated High
Launches a web UI server process, triggering external operations with uncertain side effects.
From the tool's definition Start server on demand, searches for free port, returns local HTTP URL.
Attacks that exploit this kind of access
The rule that runs start_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 start_ui, this is the rule to start with:
start_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Project Guardian MCP, apply this rule, and every start_ui call is checked against it from then on.
Questions about start_ui
Start the Project Guardian Web UI server on demand. Automatically searches for a free port and returns the local HTTP URL. 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.
Register the Project Guardian MCP server in PolicyLayer and add a rule for start_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.
start_ui 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 start_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.
Set action: deny in the PolicyLayer policy for start_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.
start_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.
More on Project Guardian, and thousands of servers like it.
Across the catalogue