Simple hello tool
AI agents call hello as a supporting operation in Multi Agent Orchestrator MCP workflows.
The name 'hello' and description 'Simple hello tool' strongly suggest this is a basic greeting/test tool with no meaningful side effects. However, the description is nearly empty, which lowers confidence.
From the tool's definition Tool name: 'hello', description: 'Simple hello tool' — description is uninformative and provides no detail about what the tool actually does.
Attacks that exploit this kind of access
Simple hello tool. It is categorised as a Other tool in the Multi Agent Orchestrator MCP MCP Server, which means it performs auxiliary operations.
Register the Multi Agent Orchestrator 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 Multi Agent Orchestrator MCP. Nothing to install.
hello is a Other 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 Multi Agent Orchestrator MCP server (ssdeanx/orchestrator-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 →