setup_project · KeepGoing MCP Server MCP: Risk & Policy

WHAT IT DOES

What setup_project does on KeepGoing MCP Server

AI agents use setup_project to create or update resources in KeepGoing MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your KeepGoing MCP Server environment.

WHY IT NEEDS A POLICY

Why setup_project needs a policy

This tool performs setup operations that create or modify project configuration (hooks and instructions), making it a Write operation. It is not Read (which would only retrieve information), not Execute (which would run arbitrary code with variable effects), and not Destructive (the setup can be undone by removing hooks).

From the tool's definition The tool description states 'Set up KeepGoing hooks and instructions' which indicates it creates or modifies configuration and system hooks within a project. This is a reversible change operation that establishes persistent tracking mechanisms.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_project Rate-limited

setup_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_project": {
      "limits": [
        {
          "counter": "setup_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about setup_project

What does the setup_project tool do? +

Set up KeepGoing hooks and instructions. Use scope. It is categorised as a Write tool in the KeepGoing MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setup_project? +

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

What risk level is setup_project? +

setup_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setup_project? +

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

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

setup_project is provided by the KeepGoing MCP Server MCP server (keepgoing-dev/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.