calibration.optimize_rubrics · ContextForge MCP Gateway MCP

WHAT IT DOES

What calibration.optimize_rubrics does on ContextForge MCP Gateway

AI agents use calibration.optimize_rubrics to create or update resources in ContextForge MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextForge MCP Gateway environment.

WHY IT NEEDS A POLICY

Why calibration.optimize_rubrics needs a policy

This tool modifies evaluation rubrics to optimize them for alignment with human judgments. It is a Write operation as it updates/tunes configuration or scoring criteria. Misuse could cause AI evaluation pipelines to be miscalibrated, potentially skewing quality assessments, but it does not execute code, delete data, or involve finances.

From the tool's definition 'Tune evaluation rubrics' and 'better alignment with human judgments' indicate modification of rubric/evaluation configuration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calibration.optimize_rubrics Rate-limited

calibration.optimize_rubrics stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calibration.optimize_rubrics": {
      "limits": [
        {
          "counter": "calibration.optimize_rubrics_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ContextForge MCP Gateway, so you can run agents against it safely.

FAQ

Questions about calibration.optimize_rubrics

What does the calibration.optimize_rubrics tool do? +

Tune evaluation rubrics for better alignment with human judgments. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on calibration.optimize_rubrics? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for calibration.optimize_rubrics: 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.

What risk level is calibration.optimize_rubrics? +

calibration.optimize_rubrics is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit calibration.optimize_rubrics? +

Yes. Add a rate_limit block to the calibration.optimize_rubrics 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.

How do I block calibration.optimize_rubrics completely? +

Set action: deny in the PolicyLayer policy for calibration.optimize_rubrics. 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.

What MCP server provides calibration.optimize_rubrics? +

calibration.optimize_rubrics 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.

// THE FULL RECORD

calibration.optimize_rubrics is one line of ContextForge MCP Gateway's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →