Get time-based analytics for workflow phases including cycle times, phase breakdowns, and aging metrics
AI agents call get_workflow_analytics to retrieve information from MCP GitHub Issue Priority Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only analytics retrieval tool that queries and returns time-based metrics about workflow phases. It has no side effects on data, does not execute code or commands, does not modify or delete resources, and does not involve financial operations. The lowest severity applies because misuse by an AI agent would only result in retrieving analytics information, posing no destructive or operational risk.
From the tool's definition Tool name is 'get_workflow_analytics' and description states it 'Get[s] time-based analytics for workflow phases including cycle times, phase breakdowns, and aging metrics' — purely retrieves and queries analytics data with no modification, deletion, or…
Attacks that exploit this kind of access
Get time-based analytics for workflow phases including cycle times, phase breakdowns, and aging metrics. It is categorised as a Read tool in the MCP GitHub Issue Priority Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GitHub Issue Priority Server MCP server in PolicyLayer and add a rule for get_workflow_analytics: 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 MCP GitHub Issue Priority Server. Nothing to install.
get_workflow_analytics 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 get_workflow_analytics 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 get_workflow_analytics. 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.
get_workflow_analytics is provided by the MCP GitHub Issue Priority Server MCP server (steiner385/mcp-git-issue-priority). 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 →