Echo back a message after a simulated delay.
AI agents call echo_with_delay to retrieve information from MCP Echo Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is purely reflective and returns data without side effects. It matches the Read category definition: retrieves or queries data with no side effects. The delay is simulated and does not constitute an Execute action since no external operations, code execution, or commands are triggered.
From the tool's definition Tool description states it 'Echo back a message after a simulated delay' — it receives input and returns it without modification or side effects. No data creation, modification, deletion, code execution, or financial operations occur.
Attacks that exploit this kind of access
Echo back a message after a simulated delay. It is categorised as a Read tool in the MCP Echo Service MCP Server, which means it retrieves data without modifying state.
Register the MCP Echo Service MCP server in PolicyLayer and add a rule for echo_with_delay: 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 MCP Echo Service. Nothing to install.
echo_with_delay 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_with_delay 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_with_delay. 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_with_delay is provided by the MCP Echo Service MCP server (nimblebraininc/mcp-echo). 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 →