Echo back the provided message.
AI agents call echo to retrieve information from Incident Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The echo tool merely returns input to the caller without side effects. It does not query, modify, execute, or delete data. While it has no meaningful security impact, it is technically a read-like operation (returning information to the caller) rather than truly benign, so Read is the appropriate classification rather than Other.
From the tool's definition Tool name is 'echo' and description states it will 'Echo back the provided message.' This is a simple reflection utility with no data retrieval, modification, execution, or destructive capability.
Attacks that exploit this kind of access
Echo back the provided message. It is categorised as a Read tool in the Incident Agent MCP Server, which means it retrieves data without modifying state.
Register the Incident Agent 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 Incident Agent. 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 Incident Agent MCP server (jayliumlp/incident-agent). 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 →