AI agents use set_context to create or update resources in Zulip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zulip environment.
With no description provided, confidence is reduced. However, given this is a Zulip bot tool and 'set_context' most likely modifies bot state or conversation context (similar to how 'edit_message' modifies messages), it appears to be a Write operation that creates or modifies data reversibly. This is typical for context management in chat systems.
From the tool's definition Tool name 'set_context' in Zulip chat context; sibling tools include 'add_reaction', 'edit_message', and other message manipulation operations.
Documented attack patterns abuse exactly the kind of access set_context 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 set_context:
{
"version": "1",
"default": "deny",
"tools": {
"set_context": {
"limits": [
{
"counter": "set_context_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_context stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
set_context. It is categorised as a Write tool in the Zulip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zulip MCP server in PolicyLayer and add a rule for set_context: 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.
set_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_context 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 set_context. 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.
set_context 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.