Say hello to the world
AI agents call say-hello to retrieve information from MCP-TS-DEMO without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or generates a static greeting response with no side effects, state changes, or operations on underlying data. It falls clearly into the Read category as a harmless informational output.
From the tool's definition Tool name 'say-hello' and description 'Say hello to the world' indicate a simple greeting output with no data modification, deletion, or external operation execution.
Attacks that exploit this kind of access
Say hello to the world. It is categorised as a Read tool in the MCP-TS-DEMO MCP Server, which means it retrieves data without modifying state.
Register the MCP-TS-DEMO MCP server in PolicyLayer and add a rule for say-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 MCP-TS-DEMO. Nothing to install.
say-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 say-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 say-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.
say-hello is provided by the MCP-TS-DEMO MCP server (pjqdyd/mcp-ts-demo). 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 →