New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_project_token

Mint a PROJECT-scoped management token (er_mcp_) for MCP and REST; it cannot authenticate relay traffic. Use it after create_project to configure a fresh project, or for any project you already own. Attenuated by design: the scopes must be a subset of THIS token's own grant (read is always includ...

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev
Medium RISK CLASS
Category Write
Parameters 42 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-echorelay-management/create-project-token.md

What create_project_token does on EchoRelay

AI agents use create_project_token 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.

ParameterTypeRequiredDescription
slug string Yes The slug of a project you own.
label string Yes Human-readable token label (1–100 chars).
scopes array Scopes for the minted token — must be a subset of this token's own scopes. `read` is always granted. `spend` and the legacy `billing` scope are never mintable h
expiresInDays integer Days until the minted token expires. Default 30. API-minted tokens always expire.

Parameters from the server's own tool schema.

Why create_project_token is rated Medium

An AI agent can call create_project_token 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.

Questions about create_project_token

What does the create_project_token tool do? +

Mint a PROJECT-scoped management token (er_mcp_) for MCP and REST; it cannot authenticate relay traffic. Use it after create_project to configure a fresh project, or for any project you already own. Attenuated by design: the scopes must be a subset of THIS token's own grant (read is always included), expiry is mandatory (1–90 days, default 30, never "never"), and the minted token — being project-scoped — can never mint tokens itself. spend is human-granted only: no token, of any scope, can mint one carrying it — mint a spend-scoped key from the project's panel instead. Requires an ACCOUNT-scoped token and the config scope. Returns the plaintext exactly once; only its hash is stored. 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.

What parameters does create_project_token accept? +

create_project_token accepts 4 parameters: slug, label, scopes, expiresInDays. Required: slug, label. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_project_token? +

Register the EchoRelay MCP server in PolicyLayer and add a rule for create_project_token: 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.

What risk level is create_project_token? +

create_project_token is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_project_token? +

Yes. Add a rate_limit block to the create_project_token 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.

How do I block create_project_token completely? +

Set action: deny in the PolicyLayer policy for create_project_token. 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.

What MCP server provides create_project_token? +

create_project_token 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of EchoRelay's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.