AI agents invoke boss_filter_and_score to trigger actions in Boss Zhipin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an automated pipeline that filters and scores candidates stored in the database. It triggers a computation/decision process over existing data rather than simply reading it or writing new records. The scoring may modify stored scores or rankings (Write), but the primary action is running an automated evaluation workflow, making Execute the most appropriate category.
From the tool's definition 自动筛选 + 评分数据库中的候选人 (automatically filters and scores candidates in the database)
Documented attack patterns abuse exactly the kind of access boss_filter_and_score 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_filter_and_score:
{
"version": "1",
"default": "deny",
"tools": {
"boss_filter_and_score": {
"limits": [
{
"counter": "boss_filter_and_score_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}boss_filter_and_score stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
自动筛选 + 评分数据库中的候选人。. It is categorised as a Execute tool in the Boss Zhipin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Boss Zhipin MCP server in PolicyLayer and add a rule for boss_filter_and_score: 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_filter_and_score is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the boss_filter_and_score 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_filter_and_score. 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_filter_and_score 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.