gluecron_fork_repo
Fork a repository to the authenticated caller's namespace. Mirrors POST /:owner/:repo/fork. Returns {owner, repo, url}. Requires 'repo' scope.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-fork-repo.md
What gluecron_fork_repo does on Gluecron
AI agents use gluecron_fork_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 | Source repo name |
owner | string | Yes | Source repo owner |
Parameters from the server's own tool schema.
Why gluecron_fork_repo is rated Medium
Forking a repository is a reversible write operation that creates new data (a repository copy) but does not delete, destroy, or irreversibly modify existing data. The blast radius is medium: an attacker could fork repositories without permission, potentially creating clutter or exfiltrating code, but the operation is reversible (the fork can be deleted) and does not directly execute code, destroy data, or move money.
From the tool's definition Tool description states 'Fork a repository' — this creates a new copy of a repository under the caller's namespace. The verb 'fork' combined with 'Mirrors POST /:owner/:repo/fork' confirms it performs a create operation.
Attacks that exploit this kind of access
The rule that runs gluecron_fork_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_fork_repo, this is the rule to start with:
gluecron_fork_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_fork_repo call is checked against it from then on.
Questions about gluecron_fork_repo
Fork a repository to the authenticated caller's namespace. Mirrors POST /:owner/:repo/fork. Returns {owner, repo, url}. Requires 'repo' scope. 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_fork_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_fork_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_fork_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_fork_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_fork_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_fork_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