New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gluecron_update_repo

Update repository description / visibility / default_branch. Owner-only. Requires 'repo' scope. Returns {ok: true}.

SERVERGluecron SOURCEhttps://gluecron.com/mcp
Medium RISK CLASS
Category Write
Parameters 52 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about gluecron_update_repo

What does the gluecron_update_repo tool do? +

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.

What parameters does gluecron_update_repo accept? +

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.

How do I enforce a policy on gluecron_update_repo? +

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.

What risk level is gluecron_update_repo? +

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

Can I rate-limit gluecron_update_repo? +

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.

How do I block gluecron_update_repo completely? +

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.

What MCP server provides gluecron_update_repo? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gluecron's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.