AI agents call greet_user to retrieve information from Mcp Rag Local without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward greeting action that reads user context (name) and outputs a message. It has no side effects, does not create or modify data, does not execute code or commands, and does not delete or move resources. It is informational only, consistent with the Read category for non-destructive data retrieval or display operations.
From the tool's definition Tool name 'greet_user' and description 'Greet the user with their name and the server's name' indicate a simple greeting operation that retrieves or displays information without modifying data or triggering external operations.
Documented attack patterns abuse exactly the kind of access greet_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Rag Local, and nothing reaches the server without passing your rules. This is the rule we recommend for greet_user:
{
"version": "1",
"default": "deny",
"tools": {
"greet_user": {}
}
}greet_user is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Greet the user with their name and the server's name. It is categorised as a Read tool in the Mcp Rag Local MCP Server, which means it retrieves data without modifying state.
Register the Mcp Rag Local MCP server in PolicyLayer and add a rule for greet_user: 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 Rag Local. Nothing to install.
greet_user 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 greet_user 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 greet_user. 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.
greet_user is provided by the Mcp Rag Local MCP server (renl/mcp-rag-local). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Rag Local, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Mcp Rag Local tools catalogued and risk-classified — across an index of 43,000+ MCP servers.