vibecontrols_components_fork_git_hub_repo

Fork or create a GitHub repo for component setup. Returns { isForked, repoFullName, repoUrl }.

SERVERVibecontrols SOURCE@vibecontrols/mcp

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-components-fork-git-hub-repo.md

WHAT IT DOES

What vibecontrols_components_fork_git_hub_repo does on Vibecontrols

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

Parameter	Type	Required	Description
`scope`	string	Yes	USER or ORG
`token`	string	—	Personal access token (if no connection)
`orgName`	string	—	Org name (required when scope=ORG)
`repoName`	string	Yes	Name of the new repository
`description`	string	—	Repository description
`connectionId`	string	—	OAuth connection ID
`sourceRepoUrl`	string	—	Source repo URL to fork

Parameters from the server's own tool schema.

RISK

Why vibecontrols_components_fork_git_hub_repo is rated Medium

An AI agent can call vibecontrols_components_fork_git_hub_repo faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (token)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_components_fork_git_hub_repo safely

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

vibecontrols_components_fork_git_hub_repo Rate-limited

vibecontrols_components_fork_git_hub_repo 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": {
    "vibecontrols_components_fork_git_hub_repo": {
      "limits": [
        {
          "counter": "vibecontrols_components_fork_git_hub_repo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_components_fork_git_hub_repo call is checked against it from then on.

FAQ

Questions about vibecontrols_components_fork_git_hub_repo

What does the vibecontrols_components_fork_git_hub_repo tool do? +

Fork or create a GitHub repo for component setup. Returns { isForked, repoFullName, repoUrl }. It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does vibecontrols_components_fork_git_hub_repo accept? +

vibecontrols_components_fork_git_hub_repo accepts 7 parameters: scope, token, orgName, repoName, description, connectionId, sourceRepoUrl. Required: scope, repoName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_components_fork_git_hub_repo? +

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

What risk level is vibecontrols_components_fork_git_hub_repo? +

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

Can I rate-limit vibecontrols_components_fork_git_hub_repo? +

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

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

vibecontrols_components_fork_git_hub_repo is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vibecontrols, and thousands of servers like it.

This server

All 672 Vibecontrols tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →