AI agents call boss_query_db 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 strongly suggests querying a database for information retrieval, which is a Read operation. Without a description, confidence is moderate, but the sibling tools (filter_and_score, evaluate_candidate, export_report) suggest this server performs recruitment analytics on existing data rather than destructive operations. No evidence of side effects beyond retrieving candidate or job data.
From the tool's definition Tool name 'boss_query_db' contains 'query' and 'db' (database), indicating data retrieval; no description provided to confirm scope or reveal modification/deletion capabilities.
Documented attack patterns abuse exactly the kind of access boss_query_db 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_query_db:
{
"version": "1",
"default": "deny",
"tools": {
"boss_query_db": {}
}
}boss_query_db 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_query_db. 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_query_db: 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_query_db 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_query_db 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_query_db. 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_query_db 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.