Simple echo tool without output schema (for comparison)
AI agents call echo to retrieve information from ContextForge MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
An echo tool merely returns the input provided to it, making it a read-only operation with no side effects, data modification, or external execution. The lack of an output schema reinforces that this is a simple passthrough utility. Risk is minimal unless the tool could be abused to infer information about the system, but as a basic reflection mechanism, it represents the lowest risk category.
From the tool's definition Tool is named 'echo' and described as 'Simple echo tool without output schema'. Echo tools reflect input back without side effects, modification of state, or execution of external operations.
Attacks that exploit this kind of access
Simple echo tool without output schema (for comparison). It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway 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 ContextForge MCP Gateway. 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 ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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 →