baseline_vs_actual

Compare baseline vs actual metrics

SERVERContextForge MCP Gateway SOURCEjrmatherly/mcp-context-forge

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jrmatherly-mcp-context-forge/baseline-vs-actual.md

WHAT IT DOES

What baseline_vs_actual does on ContextForge MCP Gateway

AI agents call baseline_vs_actual 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.

RISK

Why baseline_vs_actual is rated Low

This tool retrieves and compares metric data. The verb 'compare' is analytical and read-only, producing no changes to underlying data, no code execution, and no irreversible actions. The low severity reflects minimal blast radius—misuse would only expose or incorrectly present metric information without enabling harmful state changes.

From the tool's definition Tool name 'baseline_vs_actual' and description 'Compare baseline vs actual metrics' indicate data retrieval and comparison operations with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs baseline_vs_actual 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 baseline_vs_actual, this is the rule to start with:

baseline_vs_actual Allowed

baseline_vs_actual is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "baseline_vs_actual": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every baseline_vs_actual call is checked against it from then on.

FAQ

Questions about baseline_vs_actual

What does the baseline_vs_actual tool do? +

Compare baseline vs actual metrics. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on baseline_vs_actual? +

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

baseline_vs_actual is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit baseline_vs_actual? +

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

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

baseline_vs_actual 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.

KEEP EXPLORING

More on ContextForge MCP Gateway, and thousands of servers like it.

This server

All 221 ContextForge MCP Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →