Super admin greeting requiring both admin scopes AND super-admin role
AI agents call super-admin-greet 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 appears to be a greeting/message retrieval function that requires elevated permissions (super-admin role and admin scopes). Greetings are read-only operations that return informational messages. The elevated permission requirement suggests it may expose sensitive information visible only to super-admins, raising severity slightly, but it remains a read operation with no side effects.
From the tool's definition Super admin greeting requiring both admin scopes AND super-admin role
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Super admin greeting requiring both admin scopes AND super-admin role. 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 super-admin-greet: 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.
super-admin-greet 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 super-admin-greet 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 super-admin-greet. 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.
super-admin-greet 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 →