web_setup_project · PC-Control MCP Server MCP: Risk & Policy

WHAT IT DOES

What web_setup_project does on PC-Control MCP Server

AI agents invoke web_setup_project to trigger actions in PC-Control MCP Server. 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 IT NEEDS A POLICY

Why web_setup_project needs a policy

Setting up a project involves running package manager commands, creating directories, writing files, and potentially installing dependencies. On a PC-Control server that explicitly 'executes shell commands', this tool triggers external operations on the host OS. It spans Write (creates files) and Execute (runs commands), and Execute is more severe.

From the tool's definition 'Setup a new frontend project with a specified template' — creates project scaffolding by executing shell commands (npm/yarn/etc.) on the host system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

web_setup_project Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PC-Control MCP Server, so you can run agents against it safely.

FAQ

Questions about web_setup_project

What does the web_setup_project tool do? +

Setup a new frontend project with a specified template. It is categorised as a Execute tool in the PC-Control MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on web_setup_project? +

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

What risk level is web_setup_project? +

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

Can I rate-limit web_setup_project? +

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

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

web_setup_project is provided by the PC-Control MCP Server MCP server (krsnmlna1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.