repository_create · Semaphore MCP: Risk & Policy

WHAT IT DOES

What repository_create does on Semaphore

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

WHY IT NEEDS A POLICY

Why repository_create needs a policy

Based on naming convention and server context managing Semaphore automation workflows, this tool most likely creates a new repository resource in the Semaphore system. This is a reversible Write operation (can be deleted via sibling repository_delete if it exists).

From the tool's definition Tool named 'repository_create' with no description provided; sibling tools show patterns of Create/Delete/Get/List operations on infrastructure resources (environment_create, inventory_create, key_delete). The 'create' suffix indicates data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

repository_create Rate-limited

repository_create 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": {
    "repository_create": {
      "limits": [
        {
          "counter": "repository_create_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 Semaphore, so you can run agents against it safely.

FAQ

Questions about repository_create

What does the repository_create tool do? +

repository_create. It is categorised as a Write tool in the Semaphore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on repository_create? +

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

What risk level is repository_create? +

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

Can I rate-limit repository_create? +

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

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

repository_create is provided by the Semaphore MCP server (vitexsoftware/semaphore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.