Generate pipeline status dashboard with issue counts per workflow phase, health indicators, and formatted output. Fetches all project items (full project scan, no silent 500-cap) so phase counts reflect every item regardless of board position. Returns structured data with optional markdown or ASC...
AI agents call ralph_hero__pipeline_dashboard to retrieve information from Ralph Hero without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates GitHub project data to produce a dashboard view. It performs read-only operations (fetching project items, counting issues) and returns formatted output for display. There are no side effects mentioned—no creation, modification, deletion, or execution of external operations.
From the tool's definition Tool description states it 'Generate[s] pipeline status dashboard' and 'Fetches all project items' to display 'issue counts per workflow phase, health indicators, and formatted output'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Generate pipeline status dashboard with issue counts per workflow phase, health indicators, and formatted output. Fetches all project items (full project scan, no silent 500-cap) so phase counts reflect every item regardless of board position. Returns structured data with optional markdown or ASCII rendering. Top-level. It is categorised as a Read tool in the Ralph Hero MCP Server, which means it retrieves data without modifying state.
Register the Ralph Hero MCP server in PolicyLayer and add a rule for ralph_hero__pipeline_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 Ralph Hero. Nothing to install.
ralph_hero__pipeline_dashboard 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 ralph_hero__pipeline_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.
Set action: deny in the PolicyLayer policy for ralph_hero__pipeline_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.
ralph_hero__pipeline_dashboard is provided by the Ralph Hero MCP server (ralph-hero-mcp-server). 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 →