replace_parent
When true, replaces the sub-issue's current parent issue. Use with 'add' method only. (boolean, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/replace-parent.md
What replace_parent does on GitHub
AI agents use replace_parent to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
Why replace_parent is rated Medium
This tool modifies existing data (the parent relationship of a sub-issue) but does not delete or irreversibly destroy data. It changes a reference/link between issues, which is a reversible write operation. The impact is scoped to issue hierarchy metadata rather than content deletion, placing it in the Write category.
From the tool's definition Tool name 'replace_parent' and description states it 'replaces the sub-issue's current parent issue,' indicating modification of issue relationships/metadata.
Attacks that exploit this kind of access
The rule that runs replace_parent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For replace_parent, this is the rule to start with:
replace_parent 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 GitHub, apply this rule, and every replace_parent call is checked against it from then on.
Questions about replace_parent
When true, replaces the sub-issue's current parent issue. Use with 'add' method only. (boolean, optional). It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub MCP server in PolicyLayer and add a rule for replace_parent: 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 GitHub. Nothing to install.
replace_parent 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 replace_parent 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 replace_parent. 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.
replace_parent is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue