get_project
Get the EchoRelay project this token is scoped to: id, slug, name, caller-facing API base URL, whether the token has edit access, and the request-log hot-tier retention window.
This record as markdown: /tools/dev-echorelay-management/get-project.md
What get_project does on EchoRelay
AI agents call get_project to retrieve information from EchoRelay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_project is rated Low
This tool retrieves project metadata and configuration without creating, modifying, deleting, or executing operations. It is purely informational, returning project attributes scoped to the authenticated token. The low severity reflects minimal blast radius—even if misused by an agent, it only exposes metadata about a project already accessible to the token holder.
From the tool's definition Tool description explicitly states it 'Get[s]' project information (id, slug, name, API base URL, token edit access, retention window). The verb 'Get' and the read-only nature of retrieving configuration metadata indicate no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_project, this is the rule to start with:
get_project is read-only, so it stays allowed. 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 get_project call is checked against it from then on.
Questions about get_project
Get the EchoRelay project this token is scoped to: id, slug, name, caller-facing API base URL, whether the token has edit access, and the request-log hot-tier retention window. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
Register the EchoRelay MCP server in PolicyLayer and add a rule for get_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.
get_project is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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