AI agents call boss_multi_search to retrieve information from Boss Zhipin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context indicate this performs candidate search operations within a recruitment platform. Search is fundamentally a Read operation that retrieves data without modification. However, the empty description and context of automated recruitment (where search results feed into scoring/filtering) introduces moderate risk if an agent over-searches or exfiltrates candidate data at scale.
From the tool's definition Tool name 'boss_multi_search' implies querying/searching for candidates in BOSS直聘 recruitment system. Sibling tools like 'boss_query_db' and 'boss_filter_and_score' confirm this server retrieves candidate data. No description provided, lowering confidence.
Documented attack patterns abuse exactly the kind of access boss_multi_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Boss Zhipin, and nothing reaches the server without passing your rules. This is the rule we recommend for boss_multi_search:
{
"version": "1",
"default": "deny",
"tools": {
"boss_multi_search": {}
}
}boss_multi_search 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.
boss_multi_search. It is categorised as a Read tool in the Boss Zhipin MCP Server, which means it retrieves data without modifying state.
Register the Boss Zhipin MCP server in PolicyLayer and add a rule for boss_multi_search: 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 Boss Zhipin. Nothing to install.
boss_multi_search 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 boss_multi_search 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 boss_multi_search. 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.
boss_multi_search is provided by the Boss Zhipin MCP server (snseam/boss-zhipin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Boss Zhipin, 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.
17 Boss Zhipin tools catalogued and risk-classified — across an index of 43,000+ MCP servers.