proxy_start

Start local reverse proxy (Caddy) with HTTPS for local development.

SERVERYaver SOURCEyaver-cli

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/io-github-kivanccakmak-yaver/proxy-start.md

WHAT IT DOES

What proxy_start does on Yaver

AI agents invoke proxy_start to trigger actions in Yaver. 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 proxy_start is rated High

This tool triggers an external operation (starting Caddy reverse proxy) whose effects depend on arguments and system state. While primarily for local development, it launches a privileged process that intercepts and forwards network traffic. This is Execute rather than Write because it runs code/services rather than creating reversible data structures.

From the tool's definition Tool 'proxy_start' starts a local reverse proxy (Caddy) with HTTPS, which executes a network daemon with elevated privileges and configures system networking.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxy_start safely

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

proxy_start Rate-limited

proxy_start 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": {
    "proxy_start": {
      "limits": [
        {
          "counter": "proxy_start_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 Yaver, apply this rule, and every proxy_start call is checked against it from then on.

FAQ

Questions about proxy_start

What does the proxy_start tool do? +

Start local reverse proxy (Caddy) with HTTPS for local development. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on proxy_start? +

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

What risk level is proxy_start? +

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

Can I rate-limit proxy_start? +

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

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

proxy_start is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

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