get_key_policy

Returns the project's key policy: defaultKeyTtlDays, maxKeyTtlDays, editorsMayCreateNonExpiringKeys.

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-echorelay-management/get-key-policy.md

WHAT IT DOES

What get_key_policy does on EchoRelay

AI agents call get_key_policy 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.

RISK

Why get_key_policy is rated Low

This tool queries and retrieves policy settings. It performs a read-only operation on existing data without creating, modifying, deleting, or executing any operations. The action is informational only, making it a low-severity Read operation.

From the tool's definition Tool description states it 'Returns the project's key policy' — a retrietary operation that retrieves policy configuration data with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_key_policy 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_key_policy, this is the rule to start with:

get_key_policy Allowed

get_key_policy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_key_policy": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every get_key_policy call is checked against it from then on.

FAQ

Questions about get_key_policy

What does the get_key_policy tool do? +

Returns the project's key policy: defaultKeyTtlDays, maxKeyTtlDays, editorsMayCreateNonExpiringKeys. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_key_policy? +

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

get_key_policy is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_key_policy? +

Yes. Add a rate_limit block to the get_key_policy 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 get_key_policy completely? +

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

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

KEEP EXPLORING

More on EchoRelay, and thousands of servers like it.

This server

All 78 EchoRelay tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →