set_key_policy

Owner-only. Edit the project's key policy. Only fields present in the patch are touched. Editors calling this get an error — use get_key_policy to read.

SERVEREchoRelay SOURCEhttps://mcp.echorelay.dev

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What set_key_policy does on EchoRelay

AI agents use set_key_policy 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
`maxKeyTtlDays`	integer \| null	—
`defaultKeyTtlDays`	integer \| null	—
`editorsMayCreateNonExpiringKeys`	boolean	—

Parameters from the server's own tool schema.

RISK

Why set_key_policy is rated Medium

This tool creates or modifies data (key policy configuration) reversibly. While it affects security posture (key policies control API key access), it does not execute code, delete data irreversibly, or move money. The high severity reflects that misconfiguring key policies could grant unintended access, but the change is reversible via subsequent calls to set_key_policy.

From the tool's definition Tool description states 'Edit the project's key policy' and 'Only fields present in the patch are touched', indicating modification of configuration data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_key_policy Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_key_policy": {
      "limits": [
        {
          "counter": "set_key_policy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about set_key_policy

What does the set_key_policy tool do? +

Owner-only. Edit the project's key policy. Only fields present in the patch are touched. Editors calling this get an error — use get_key_policy to read. 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 set_key_policy accept? +

set_key_policy accepts 3 parameters: maxKeyTtlDays, defaultKeyTtlDays, editorsMayCreateNonExpiringKeys. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_key_policy? +

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

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

Can I rate-limit set_key_policy? +

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

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

set_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

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →