Analyzes engineering metrics (commit frequency, deploy failure rate, tech debt) and produces an Execution Stability Score (1-100). Use when the user provides development/repo activity data as JSON.
AI agents call analyze_execution_stability to retrieve information from openGlad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and analyzes metrics (commit frequency, deploy failure rate, tech debt) from provided JSON data to generate a diagnostic score. No side effects, no data modification, no code execution, no destructive operations. The output is purely informational analysis, making this a Read category tool with low severity since misuse would only result in incorrect analysis, not system damage or data loss.
From the tool's definition Tool 'analyzes engineering metrics' and 'produces' a score based on provided data; it retrieves and processes existing development/repo activity data without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access analyze_execution_stability gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and openGlad, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_execution_stability:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_execution_stability": {}
}
}analyze_execution_stability is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyzes engineering metrics (commit frequency, deploy failure rate, tech debt) and produces an Execution Stability Score (1-100). Use when the user provides development/repo activity data as JSON. It is categorised as a Read tool in the openGlad MCP Server, which means it retrieves data without modifying state.
Register the openGlad MCP server in PolicyLayer and add a rule for analyze_execution_stability: 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 openGlad. Nothing to install.
analyze_execution_stability 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 analyze_execution_stability 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 analyze_execution_stability. 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.
analyze_execution_stability is provided by the openGlad MCP server (tuguberk/openglad). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from openGlad, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 openGlad tools catalogued and risk-classified — across an index of 43,000+ MCP servers.