Register an existing local Git repo under an allowed root. Requires LLM_GATEWAY_WORKSPACE_ADMIN=1 and OAuth scope workspace:admin.
AI agents use workspace_register_existing_repo to create or update resources in LLM CLI Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LLM CLI Gateway environment.
This tool creates a new workspace registration in a centralized gateway managing multiple LLM CLI endpoints. While it does not delete data (ruling out Destructive), and performs no financial transaction, it modifies the system's workspace configuration in a way that could expose or lock in access to repositories.
From the tool's definition Tool description states 'Register an existing local Git repo' — a registration operation that creates or records a new workspace reference.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access workspace_register_existing_repo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LLM CLI Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for workspace_register_existing_repo:
{
"version": "1",
"default": "deny",
"tools": {
"workspace_register_existing_repo": {
"limits": [
{
"counter": "workspace_register_existing_repo_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}workspace_register_existing_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.
Free to start. No card required.
Register an existing local Git repo under an allowed root. Requires LLM_GATEWAY_WORKSPACE_ADMIN=1 and OAuth scope workspace:admin. It is categorised as a Write tool in the LLM CLI Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LLM CLI Gateway MCP server in PolicyLayer and add a rule for workspace_register_existing_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 LLM CLI Gateway. Nothing to install.
workspace_register_existing_repo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workspace_register_existing_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.
Set action: deny in the PolicyLayer policy for workspace_register_existing_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.
workspace_register_existing_repo is provided by the LLM CLI Gateway MCP server (llm-cli-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LLM CLI Gateway, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
46 LLM CLI Gateway tools catalogued and risk-classified — across an index of 43,000+ MCP servers.