protect_project
Turn on archive protection for a project you own: archive_project (on every surface — panel, REST, and this tool) then refuses until it is lifted. Idempotent. Permanent from here — there is no tool or API call to turn it back off; only contacting support can. Requires an ACCOUNT-scoped token and ...
This record as markdown: /tools/dev-echorelay-management/protect-project.md
What protect_project does on EchoRelay
AI agents use protect_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 |
|---|---|---|---|
slug | string | Yes | The slug of a project you own. |
Parameters from the server's own tool schema.
Why protect_project is rated Medium
An AI agent can call protect_project faster than any human can review: one bad instruction and it creates or modifies resources in EchoRelay by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs protect_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 protect_project, this is the rule to start with:
protect_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 protect_project call is checked against it from then on.
Questions about protect_project
Turn on archive protection for a project you own: archive_project (on every surface — panel, REST, and this tool) then refuses until it is lifted. Idempotent. Permanent from here — there is no tool or API call to turn it back off; only contacting support can. Requires an ACCOUNT-scoped token and the config scope. 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.
protect_project accepts 1 parameter: slug. Required: 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 protect_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.
protect_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 protect_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 protect_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.
protect_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