echo_value

THE RISK

Low Risk

Why echo_value needs a policy

This tool retrieves or returns user-provided input without modifying state, querying external systems, or performing irreversible operations. It is a read-only informational tool with minimal blast radius if misused by an agent.

From the tool's definition Tool description states 'Return the provided value as markdown' — a simple echo/reflection operation with no side effects or data mutation.

Documented attack patterns abuse exactly the kind of access echo_value gives an agent:

POLICY

How to control echo_value

PolicyLayer is an MCP gateway — it sits between your AI agents and Ktx, and nothing reaches the server without passing your rules. This is the rule we recommend for echo_value:

policy.json

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

echo_value is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Ktx — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ktx tools

Destructive delete_integration_file Delete one allowed integration worktree file when the failed patch proves the deletion is Write record_verification_ledger Record the pre-write verification ledger required by loaded ingest skills. Call this befor Write write_integration_file Replace one allowed integration worktree file with repaired text content. Write write_repair_file Replace one allowed integration worktree file with repaired text content. Read load_skill Load a skill to get specialized instructions. Call this when a skill listed in the system Read read_failed_patch Read the failed Git patch that could not be applied to the integration worktree. Read read_gate_error Read the artifact gate failure that must be repaired. Read read_integration_file Read one allowed file from the current integration worktree.

All 10 Ktx tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about echo_value

What does the echo_value tool do? +

Return the provided value as markdown. It is categorised as a Read tool in the Ktx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on echo_value? +

Register the Ktx MCP server in PolicyLayer and add a rule for echo_value: 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 Ktx. Nothing to install.

What risk level is echo_value? +

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

Can I rate-limit echo_value? +

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

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

echo_value is provided by the Ktx MCP server (kaelio/ktx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ktx tool call.

Start from Ktx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →