project_health_dashboard

Produce project health dashboard summary

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/project-health-dashboard.md

WHAT IT DOES

What project_health_dashboard does on ContextForge MCP Gateway

AI agents call project_health_dashboard 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 project_health_dashboard is rated Low

This tool retrieves and aggregates project health information to display a summary view. It has no data mutation, deletion, code execution, or financial impact. The dashboard is generated from existing data sources and serves a reporting/analytics function, consistent with the Read category for query and data retrieval operations.

From the tool's definition Tool name 'project_health_dashboard' and description 'Produce project health dashboard summary' indicate data retrieval and reporting.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

project_health_dashboard Allowed

project_health_dashboard 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": {
    "project_health_dashboard": {}
  }
}

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 project_health_dashboard call is checked against it from then on.

FAQ

Questions about project_health_dashboard

What does the project_health_dashboard tool do? +

Produce project health dashboard summary. 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 project_health_dashboard? +

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

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

Can I rate-limit project_health_dashboard? +

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

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

project_health_dashboard 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 →