Unlinks a forked project from its parent project
AI agents use unlink_fork_parent to create or update resources in Keyshade — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keyshade environment.
Unlinking a fork from its parent modifies the relationship between projects, which is a reversible write operation (the fork still exists, but its association is removed). However, this could have significant consequences for secret inheritance and synchronization in a secrets management platform, warranting a high severity rating. It is not truly destructive as the projects themselves are not deleted.
From the tool's definition Unlinks a forked project from its parent project
Documented attack patterns abuse exactly the kind of access unlink_fork_parent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Keyshade, and nothing reaches the server without passing your rules. This is the rule we recommend for unlink_fork_parent:
{
"version": "1",
"default": "deny",
"tools": {
"unlink_fork_parent": {
"limits": [
{
"counter": "unlink_fork_parent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unlink_fork_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.
Free to start. No card required.
Unlinks a forked project from its parent project. It is categorised as a Write tool in the Keyshade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keyshade MCP server in PolicyLayer and add a rule for unlink_fork_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 Keyshade. Nothing to install.
unlink_fork_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 unlink_fork_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 unlink_fork_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.
unlink_fork_parent is provided by the Keyshade MCP server (keyshade-xyz/keyshade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Keyshade, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
44 Keyshade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.