[ASYNC] Rename project ID with cascading relation updates. Returns taskId.
AI agents use rename_project to create or update resources in N2n Nexus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N2n Nexus environment.
Renaming a project is a reversible modification that changes data but does not delete or destroy information. Cascading updates to related entities increase the scope but remain write operations rather than destructive.
From the tool's definition Tool description explicitly states 'Rename project' with 'cascading relation updates', indicating modification of project data and related entities. Returns taskId suggesting an asynchronous write operation.
Documented attack patterns abuse exactly the kind of access rename_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and N2n Nexus, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_project:
{
"version": "1",
"default": "deny",
"tools": {
"rename_project": {
"limits": [
{
"counter": "rename_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_project 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.
[ASYNC] Rename project ID with cascading relation updates. Returns taskId. It is categorised as a Write tool in the N2n Nexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the N2n Nexus MCP server in PolicyLayer and add a rule for rename_project: 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 N2n Nexus. Nothing to install.
rename_project 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 rename_project 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 rename_project. 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.
rename_project is provided by the N2n Nexus MCP server (n2ns/n2n-nexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from N2n Nexus, 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.
22 N2n Nexus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.