rename_project
Rename a project you own (the display name only — the slug, which is the identity in URLs / Redis, never changes). Requires an ACCOUNT-scoped token and the config scope. 404-equivalent error when you do not own the slug.
This record as markdown: /tools/dev-echorelay-management/rename-project.md
What rename_project does on EchoRelay
AI agents use rename_project to create or update resources in EchoRelay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EchoRelay environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | The new display name (1–100 chars). |
slug | string | Yes | The slug of a project you own. |
Parameters from the server's own tool schema.
Why rename_project is rated Medium
Renaming a project is a classic Write operation—it creates or modifies data reversibly. The severity is medium because misuse could cause confusion or operational disruption (e.g., renaming a critical project to an unintelligible name), but the change is easily undone and does not destroy data, execute arbitrary code, or affect billing.
From the tool's definition The tool description explicitly states it renames a project (modifies data) by changing 'the display name'. This is a reversible modification of project metadata, not retrieval, code execution, deletion, or financial transaction.
Attacks that exploit this kind of access
The rule that runs rename_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EchoRelay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_project, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every rename_project call is checked against it from then on.
Questions about rename_project
Rename a project you own (the display name only — the slug, which is the identity in URLs / Redis, never changes). Requires an ACCOUNT-scoped token and the config scope. 404-equivalent error when you do not own the slug. It is categorised as a Write tool in the EchoRelay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
rename_project accepts 2 parameters: name, slug. Required: name, slug. The full parameter table on this page comes from the server's own tool schema.
Register the EchoRelay 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 EchoRelay. 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 EchoRelay MCP server (https://mcp.echorelay.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EchoRelay, and thousands of servers like it.
This server
Across the catalogue