server.get_available_judges
Get list of available judge models and their capabilities
This record as markdown: /tools/jrmatherly-mcp-context-forge/server.get-available-judges.md
What server.get_available_judges does on ContextForge MCP Gateway
AI agents call server.get_available_judges to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why server.get_available_judges is rated Low
This tool retrieves metadata about available judge models. It performs only a read operation—querying and returning information about existing resources without creating, modifying, deleting, or executing any logic. The passive verb 'Get' and the informational nature of the return value (list and capabilities) confirm this is a safe Read classification.
From the tool's definition Tool name 'get_available_judges' and description 'Get list of available judge models and their capabilities' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs server.get_available_judges safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For server.get_available_judges, this is the rule to start with:
server.get_available_judges is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every server.get_available_judges call is checked against it from then on.
Questions about server.get_available_judges
Get list of available judge models and their capabilities. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for server.get_available_judges: 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 ContextForge MCP Gateway. Nothing to install.
server.get_available_judges 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 server.get_available_judges 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 server.get_available_judges. 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.
server.get_available_judges is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue