Compare baseline vs actual metrics
AI agents call baseline_vs_actual to retrieve information from ContextForge MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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.
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.
baseline_vs_actual 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 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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →