coding_repo_add

Add a repo to a coding instance. A coding repo is BOTH a local checkout the engine runs in AND its GitHub identity, set together in this one call:

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/coding-repo-add.md

WHAT IT DOES

What coding_repo_add does on ProAgentStore

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

RISK

Why coding_repo_add is rated Medium

Creates or modifies coding instance configuration and repository associations, reversible changes with moderate blast radius.

From the tool's definition Add a repo to a coding instance, GitHub identity, set together in this call.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs coding_repo_add safely

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

coding_repo_add Rate-limited

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

FAQ

Questions about coding_repo_add

What does the coding_repo_add tool do? +

Add a repo to a coding instance. A coding repo is BOTH a local checkout the engine runs in AND its GitHub identity, set together in this one call:. It is categorised as a Write tool in the ProAgentStore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on coding_repo_add? +

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

What risk level is coding_repo_add? +

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

Can I rate-limit coding_repo_add? +

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

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

coding_repo_add is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

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