gluecron_delete_repo
Permanently delete a repository row (git data on disk is left untouched). Owner-only. Requires 'admin' scope. Returns {deleted: true}.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-delete-repo.md
What gluecron_delete_repo does on Gluecron
AI agents call gluecron_delete_repo to permanently remove resources in Gluecron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | Repo name |
owner | string | Yes | Repo owner username |
Parameters from the server's own tool schema.
Why gluecron_delete_repo is rated Critical
This tool irreversibly removes a repository record from the system. Although the description notes that 'git data on disk is left untouched,' the permanent deletion of the repository row itself constitutes an irreversible action that cannot be undone, fitting the Destructive category.
From the tool's definition Permanently delete a repository row ... Owner-only. Requires 'admin' scope.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs gluecron_delete_repo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_delete_repo, this is the rule to start with:
gluecron_delete_repo is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gluecron, apply this rule, and every gluecron_delete_repo call is checked against it from then on.
Questions about gluecron_delete_repo
Permanently delete a repository row (git data on disk is left untouched). Owner-only. Requires 'admin' scope. Returns {deleted: true}. It is categorised as a Destructive tool in the Gluecron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
gluecron_delete_repo accepts 2 parameters: repo, owner. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the Gluecron MCP server in PolicyLayer and add a rule for gluecron_delete_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 Gluecron. Nothing to install.
gluecron_delete_repo is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the gluecron_delete_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 gluecron_delete_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.
gluecron_delete_repo is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gluecron, and thousands of servers like it.
Across the catalogue