gluecron_update_repo
Update repository description / visibility / default_branch. Owner-only. Requires 'repo' scope. Returns {ok: true}.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-update-repo.md
What gluecron_update_repo does on Gluecron
AI agents use gluecron_update_repo to create or update resources in Gluecron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gluecron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | Repo name |
owner | string | Yes | Repo owner username |
is_private | boolean | — | Set visibility (optional) |
description | string | — | New description (optional) |
default_branch | string | — | Set default branch (optional) |
Parameters from the server's own tool schema.
Why gluecron_update_repo is rated Medium
This tool modifies repository configuration (description, visibility, default branch) but does not delete data or execute arbitrary code. These changes are reversible—the owner can restore previous values. The owner-only requirement mitigates risk but does not change the fundamental Write category.
From the tool's definition Tool name contains 'update'; description explicitly states it 'Update[s] repository description / visibility / default_branch', which are reversible metadata modifications.
Attacks that exploit this kind of access
The rule that runs gluecron_update_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_update_repo, this is the rule to start with:
gluecron_update_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gluecron, apply this rule, and every gluecron_update_repo call is checked against it from then on.
Questions about gluecron_update_repo
Update repository description / visibility / default_branch. Owner-only. Requires 'repo' scope. Returns {ok: true}. It is categorised as a Write tool in the Gluecron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
gluecron_update_repo accepts 5 parameters: repo, owner, is_private, description, default_branch. 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_update_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_update_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 gluecron_update_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_update_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_update_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.
This server
Across the catalogue