AI agents call resolve_name to retrieve information from Zulip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'resolve_name' most likely performs a read/lookup operation to resolve a user or stream name to an ID or similar identifier. No side effects are implied. However, the empty description lowers confidence significantly. Given the sibling tools are mostly read-oriented (get_*, fetch_*), this fits the Read pattern. Severity is low as name resolution is typically harmless.
From the tool's definition Tool name 'resolve_name' suggests a lookup/query operation; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access resolve_name gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zulip, and nothing reaches the server without passing your rules. This is the rule we recommend for resolve_name:
{
"version": "1",
"default": "deny",
"tools": {
"resolve_name": {}
}
}resolve_name 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.
resolve_name. It is categorised as a Read tool in the Zulip MCP Server, which means it retrieves data without modifying state.
Register the Zulip MCP server in PolicyLayer and add a rule for resolve_name: 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 Zulip. Nothing to install.
resolve_name 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 resolve_name 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 resolve_name. 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.
resolve_name is provided by the Zulip MCP server (windborne/zulipmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zulip, 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.
27 Zulip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.