AI agents call judge_workplan as a supporting operation in Yellhorn MCP workflows.
The tool name suggests it evaluates or reviews a workplan (likely a Read/Execute operation), but the empty description provides no concrete evidence of side effects, data modification, or destructive actions. Based on sibling tools (create_workplan, get_workplan, revise_workplan), this likely reads/assesses a workplan and returns feedback. Confidence is low due to the missing description.
From the tool's definition Tool name is 'judge_workplan'; description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access judge_workplan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yellhorn MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for judge_workplan:
{
"version": "1",
"default": "deny",
"tools": {
"judge_workplan": {
"limits": [
{
"counter": "judge_workplan_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}judge_workplan gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
judge_workplan. It is categorised as a Other tool in the Yellhorn MCP MCP Server, which means it performs auxiliary operations.
Register the Yellhorn MCP server in PolicyLayer and add a rule for judge_workplan: 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 Yellhorn MCP. Nothing to install.
judge_workplan is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the judge_workplan 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 judge_workplan. 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.
judge_workplan is provided by the Yellhorn MCP server (msnidal/yellhorn-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Yellhorn MCP, 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.
5 Yellhorn MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.