gluecron_repo_health
Compute the current health report for a public repo: overall score (0-100), letter grade, per-category breakdown (security/testing/complexity/dependencies/documentation/activity), and a list of insights to fix next. Backed by computeHealthScore in src/lib/intelligence.ts.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-repo-health.md
What gluecron_repo_health does on Gluecron
AI agents call gluecron_repo_health to retrieve information from Gluecron without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | Repo name |
owner | string | Yes | Repo owner username |
Parameters from the server's own tool schema.
Why gluecron_repo_health is rated Low
This tool queries repository health data and returns a read-only report with scores and insights. It has no side effects—it neither modifies repository state, deletes data, executes workflows, nor commits changes. The backing function 'computeHealthScore' in intelligence.ts is a calculation/analytics function, not a mutation or execution primitive.
From the tool's definition Tool computes and retrieves health metrics: 'overall score (0-100), letter grade, per-category breakdown...and a list of insights'. Verbs are 'Compute' and retrieve analytics; no data modification, deletion, or code execution.
Attacks that exploit this kind of access
The rule that runs gluecron_repo_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_repo_health, this is the rule to start with:
gluecron_repo_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gluecron, apply this rule, and every gluecron_repo_health call is checked against it from then on.
Questions about gluecron_repo_health
Compute the current health report for a public repo: overall score (0-100), letter grade, per-category breakdown (security/testing/complexity/dependencies/documentation/activity), and a list of insights to fix next. Backed by computeHealthScore in src/lib/intelligence.ts. It is categorised as a Read tool in the Gluecron MCP Server, which means it retrieves data without modifying state.
gluecron_repo_health accepts 2 parameters: repo, owner. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the Gluecron MCP server in PolicyLayer and add a rule for gluecron_repo_health: 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 Gluecron. Nothing to install.
gluecron_repo_health 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 gluecron_repo_health 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 gluecron_repo_health. 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.
gluecron_repo_health is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gluecron, and thousands of servers like it.
This server
Across the catalogue