シンプルなHello Worldレスポンス（テンプレート動作確認用）
AI agents call hello to retrieve information from ModelsLab Text2Image MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'hello' tool is a basic health check or template validation function that merely returns a response. It performs no data retrieval, modification, code execution, deletion, or financial operations—only outputs a confirmation message. This is a read operation with minimal security impact, suitable for verifying server connectivity or template functionality.
From the tool's definition Tool description states 'シンプルなHello Worldレスポンス（テンプレート動作確認用）' (Simple Hello World response for template operation confirmation). This is a test/diagnostic tool that returns a static response with no side effects.
Attacks that exploit this kind of access
シンプルなHello Worldレスポンス（テンプレート動作確認用）. It is categorised as a Read tool in the ModelsLab Text2Image MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ModelsLab Text2Image MCP Server MCP server in PolicyLayer and add a rule for hello: 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 ModelsLab Text2Image MCP Server. Nothing to install.
hello 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 hello 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 hello. 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.
hello is provided by the ModelsLab Text2Image MCP Server MCP server (shimizu/modelslab-text2img-mcp-server). 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 →