A sample tool that gets the user by name
AI agents call hello-world to retrieve information from NestJS MCP Server Module without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information by name without modifying, deleting, or executing any external operations. It is a straightforward Read operation with minimal risk—the blast radius of misuse is limited to potential information disclosure of user data, which is low severity without additional context indicating sensitive personal information.
From the tool's definition Tool description states it 'gets the user by name', which is a retrieval operation with no side effects. The name 'hello-world' and description indicate a simple query/lookup action.
Attacks that exploit this kind of access
A sample tool that gets the user by name. It is categorised as a Read tool in the NestJS MCP Server Module MCP Server, which means it retrieves data without modifying state.
Register the NestJS MCP Server Module MCP server in PolicyLayer and add a rule for hello-world: 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 NestJS MCP Server Module. Nothing to install.
hello-world 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-world 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-world. 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-world is provided by the NestJS MCP Server Module MCP server (rekog-labs/mcp-nest). 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 →