Echo the input text
AI agents call echo_tool to retrieve information from Cryptosense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply echoes/reflects back the input text. It has no side effects, does not modify data, and only returns what was given to it. This is a classic read/passthrough operation with minimal risk.
From the tool's definition Echo the input text
Attacks that exploit this kind of access
Echo the input text. It is categorised as a Read tool in the Cryptosense MCP Server, which means it retrieves data without modifying state.
Register the Cryptosense MCP server in PolicyLayer and add a rule for echo_tool: 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 Cryptosense. Nothing to install.
echo_tool 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_tool 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_tool. 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_tool is provided by the Cryptosense MCP server (josephibra/cryptosense-mcp). 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 →