robustness.assess_distribution_shift

WHAT IT DOES

What robustness.assess_distribution_shift does on ContextForge MCP Gateway

AI agents invoke robustness.assess_distribution_shift to trigger actions in ContextForge MCP Gateway. 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.

WHY IT NEEDS A POLICY

Why robustness.assess_distribution_shift needs a policy

This tool executes a robustness assessment by running performance tests on out-of-domain data. It triggers an active evaluation process rather than merely retrieving stored data, placing it in the Execute category. Severity is medium because misuse could consume significant compute resources or produce misleading robustness metrics, but it does not directly modify or delete data.

From the tool's definition 'Test performance degradation on out-of-domain data' — actively runs tests/assessments against data distributions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

robustness.assess_distribution_shift Rate-limited

robustness.assess_distribution_shift 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "robustness.assess_distribution_shift": {
      "limits": [
        {
          "counter": "robustness.assess_distribution_shift_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 robustness.assess_distribution_shift

What does the robustness.assess_distribution_shift tool do? +

Test performance degradation on out-of-domain data. It is categorised as a Execute tool in the ContextForge MCP Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on robustness.assess_distribution_shift? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for robustness.assess_distribution_shift: 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 robustness.assess_distribution_shift? +

robustness.assess_distribution_shift is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit robustness.assess_distribution_shift? +

Yes. Add a rate_limit block to the robustness.assess_distribution_shift 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 robustness.assess_distribution_shift completely? +

Set action: deny in the PolicyLayer policy for robustness.assess_distribution_shift. 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 robustness.assess_distribution_shift? +

robustness.assess_distribution_shift 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.