A tool that sends different greetings with delays between them
AI agents call multi-greet as a supporting operation in Codemesh workflows.
This tool sends greetings (text messages) with delays between them. It has no read, write, execute, destructive, or financial implications — it is purely a benign communication/demo tool. Severity is low as misuse has negligible blast radius.
From the tool's definition A tool that sends different greetings with delays between them
Documented attack patterns abuse exactly the kind of access multi-greet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codemesh, and nothing reaches the server without passing your rules. This is the rule we recommend for multi-greet:
{
"version": "1",
"default": "deny",
"tools": {
"multi-greet": {
"limits": [
{
"counter": "multi-greet_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} multi-greet gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
A tool that sends different greetings with delays between them. It is categorised as a Other tool in the Codemesh MCP Server, which means it performs auxiliary operations.
Register the Codemesh MCP server in PolicyLayer and add a rule for multi-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 Codemesh. Nothing to install.
multi-greet 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 multi-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 multi-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.
multi-greet is provided by the Codemesh MCP server (kiliman/codemesh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codemesh, 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.
13 Codemesh tools catalogued and risk-classified — across an index of 43,000+ MCP servers.