Return the input text unchanged. Spike validation only.
AI agents call echo to retrieve information from Threadwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool simply echoes back its input without any side effects, data modification, or external operations. It is a pure read/passthrough operation used for validation purposes only.
From the tool's definition "Return the input text unchanged. Spike validation only."
Attacks that exploit this kind of access
Return the input text unchanged. Spike validation only. It is categorised as a Read tool in the Threadwork MCP Server, which means it retrieves data without modifying state.
Register the Threadwork MCP server in PolicyLayer and add a rule for echo: 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 Threadwork. Nothing to install.
echo 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 echo 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 echo. 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.
echo is provided by the Threadwork MCP server (tianqbu/threadwork). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →