critical_path_analysis · ContextForge MCP Gateway MCP

WHAT IT DOES

What critical_path_analysis does on ContextForge MCP Gateway

AI agents invoke critical_path_analysis 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 critical_path_analysis needs a policy

Critical path analysis is a deterministic algorithm (PERT/CPM) that computes optimal paths through a project schedule. While it produces analytical output with no direct side effects on external systems, it is an 'Execute' category tool because it runs computational logic whose output depends on input data and can influence downstream decisions.

From the tool's definition Tool name contains 'run' verb equivalent ('Run critical path analysis'), and the description indicates it performs a computational operation over a schedule graph/network, which constitutes execution of an algorithm on supplied data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

critical_path_analysis Rate-limited

critical_path_analysis 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": {
    "critical_path_analysis": {
      "limits": [
        {
          "counter": "critical_path_analysis_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 critical_path_analysis

What does the critical_path_analysis tool do? +

Run critical path analysis over a schedule. 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 critical_path_analysis? +

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

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

Can I rate-limit critical_path_analysis? +

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

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

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