gluecron_repo_list_issues
List open issues for a public repository. Returns up to 50 ordered by most-recent.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-repo-list-issues.md
What gluecron_repo_list_issues does on Gluecron
AI agents call gluecron_repo_list_issues 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 |
limit | number | — | Max results, default 25 |
owner | string | Yes | Repo owner username |
Parameters from the server's own tool schema.
Why gluecron_repo_list_issues is rated Low
This tool retrieves issue metadata from a repository without modifying, deleting, or executing any operations. It is a straightforward query that returns existing data. The scope is limited to a public repository and poses no risk of unintended data modification or external system impact.
From the tool's definition Tool name contains 'list' and description states 'List open issues' with 'Returns up to 50 ordered by most-recent' — a pure data retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs gluecron_repo_list_issues 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_list_issues, this is the rule to start with:
gluecron_repo_list_issues 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_list_issues call is checked against it from then on.
Questions about gluecron_repo_list_issues
List open issues for a public repository. Returns up to 50 ordered by most-recent. It is categorised as a Read tool in the Gluecron MCP Server, which means it retrieves data without modifying state.
gluecron_repo_list_issues accepts 3 parameters: repo, limit, 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_list_issues: 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_list_issues 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_list_issues 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_list_issues. 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_list_issues 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