revoke_project_token
Revoke a PROJECT-scoped API token on a project you own — any holder's, not just your own (the account-owner kill switch for a leaked or retired integration token). Soft-revoke: the row stays for traceability and the token is rejected immediately. Idempotent. Requires an ACCOUNT-scoped token and t...
This record as markdown: /tools/dev-echorelay-management/revoke-project-token.md
What revoke_project_token does on EchoRelay
AI agents call revoke_project_token to permanently remove resources in EchoRelay, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | The slug of a project you own. |
tokenId | string | Yes | The token UUID (from create_project_token or list_project_tokens). |
Parameters from the server's own tool schema.
Why revoke_project_token is rated Critical
Revoking an API token is effectively irreversible in practice — once revoked, any integration using that token immediately loses access. While the row is retained for traceability (soft-delete), the operational effect cannot be undone (the token cannot be un-revoked without creating a new one).
From the tool's definition Revoke a PROJECT-scoped API token... the token is rejected immediately... Soft-revoke: the row stays for traceability and the token is rejected immediately.
Attacks that exploit this kind of access
The rule that runs revoke_project_token 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 revoke_project_token, this is the rule to start with:
revoke_project_token is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every revoke_project_token call is checked against it from then on.
Questions about revoke_project_token
Revoke a PROJECT-scoped API token on a project you own — any holder's, not just your own (the account-owner kill switch for a leaked or retired integration token). Soft-revoke: the row stays for traceability and the token is rejected immediately. Idempotent. Requires an ACCOUNT-scoped token and the config scope. It is categorised as a Destructive tool in the EchoRelay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
revoke_project_token accepts 2 parameters: slug, tokenId. Required: slug, tokenId. 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 revoke_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.
revoke_project_token is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revoke_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.
Set action: deny in the PolicyLayer policy for revoke_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.
revoke_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.
Across the catalogue