gluecron_search_issues
Search issues by title/body keyword on a single repo, filtered by state. Returns ranked rows.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-search-issues.md
What gluecron_search_issues does on Gluecron
AI agents call gluecron_search_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 | |
limit | number | — | |
owner | string | Yes | |
query | string | Yes | Search keyword |
state | string | — | open | closed | all (default open) |
Parameters from the server's own tool schema.
Why gluecron_search_issues is rated Low
This tool performs a search/filter operation over existing issue data and returns results. It has no side effects—it does not create, modify, delete, or execute any actions. This is a classic Read category tool: query-based retrieval of information.
From the tool's definition Tool name 'search_issues' and description 'Search issues by title/body keyword on a single repo, filtered by state. Returns ranked rows.' indicate a query operation that retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
The rule that runs gluecron_search_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_search_issues, this is the rule to start with:
gluecron_search_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_search_issues call is checked against it from then on.
Questions about gluecron_search_issues
Search issues by title/body keyword on a single repo, filtered by state. Returns ranked rows. It is categorised as a Read tool in the Gluecron MCP Server, which means it retrieves data without modifying state.
gluecron_search_issues accepts 5 parameters: repo, limit, owner, query, state. Required: repo, owner, query. 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_search_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_search_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_search_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_search_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_search_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