A simple test tool that echoes a message.
AI agents call test_tool to retrieve information from License Scanner MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The test_tool is a simple utility that reads/returns input as output. It does not create, modify, delete, or execute any operations. It poses minimal security risk as it cannot be leveraged to access sensitive data, modify systems, or trigger external actions. Classification as Read with low severity is appropriate.
From the tool's definition Tool description states 'echoes a message' with no modification, deletion, or execution of external operations. The function is purely informational and returns data without side effects.
Attacks that exploit this kind of access
A simple test tool that echoes a message. It is categorised as a Read tool in the License Scanner MCP Server MCP Server, which means it retrieves data without modifying state.
Register the License Scanner MCP Server MCP server in PolicyLayer and add a rule for test_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 License Scanner MCP Server. Nothing to install.
test_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 test_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 test_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.
test_tool is provided by the License Scanner MCP Server MCP server (ryancadby/mcp-license-scanner). 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 →