# redmine_list_issues

A read tool on the Redmine Analytics and Automation MCP Server MCP server.

Agent View of the PolicyLayer registry record for `redmine_list_issues`. HTML page: https://policylayer.com/tools/a1official-mcp/redmine-list-issues

## Facts

- Tool: `redmine_list_issues`
- Server: Redmine Analytics and Automation MCP Server (`a1official/mcp`) — https://policylayer.com/tools/a1official-mcp.md
- Homepage: https://github.com/a1official/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "redmine_list_issues",
    "arguments": {}
  }
}
```

## Why redmine_list_issues is rated Low

The tool name 'list_issues' inherently describes a retrieval operation with no side effects—it queries and returns a collection of issues from Redmine. No modification, deletion, or execution is implied. The empty description lowers confidence slightly, but the naming convention and sibling tool architecture strongly support Read classification.

From the tool's own definition: "Tool name 'redmine_list_issues' indicates a listing operation. Sibling tools include 'redmine_get_issue' and 'redmine_delete_issue', establishing a pattern where list/get operations are distinct from destructive actions."

## Use case

AI agents call redmine_list_issues to retrieve information from Redmine Analytics and Automation MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Redmine Analytics and Automation MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "redmine_list_issues": {}
  }
}
```

## Other tools on Redmine Analytics and Automation MCP Server (32)

- `redmine_delete_issue` — Destructive — https://policylayer.com/tools/a1official-mcp/redmine-delete-issue.md
- `browse_website` — Execute — https://policylayer.com/tools/a1official-mcp/browse-website.md
- `screenshot_website` — Execute — https://policylayer.com/tools/a1official-mcp/screenshot-website.md
- `play_music` — Other — https://policylayer.com/tools/a1official-mcp/play-music.md
- `extract_links` — Read — https://policylayer.com/tools/a1official-mcp/extract-links.md
- `get_artist_info` — Read — https://policylayer.com/tools/a1official-mcp/get-artist-info.md
- `redmine_backlog_analytics` — Read — https://policylayer.com/tools/a1official-mcp/redmine-backlog-analytics.md
- `redmine_cycle_time` — Read — https://policylayer.com/tools/a1official-mcp/redmine-cycle-time.md
- `redmine_get_issue` — Read — https://policylayer.com/tools/a1official-mcp/redmine-get-issue.md
- `redmine_list_projects` — Read — https://policylayer.com/tools/a1official-mcp/redmine-list-projects.md
- `redmine_list_statuses` — Read — https://policylayer.com/tools/a1official-mcp/redmine-list-statuses.md
- `redmine_list_trackers` — Read — https://policylayer.com/tools/a1official-mcp/redmine-list-trackers.md
- `redmine_list_users` — Read — https://policylayer.com/tools/a1official-mcp/redmine-list-users.md
- `redmine_list_versions` — Read — https://policylayer.com/tools/a1official-mcp/redmine-list-versions.md
- `redmine_oauth_exchange_code` — Read — https://policylayer.com/tools/a1official-mcp/redmine-oauth-exchange-code.md
- `redmine_oauth_get_auth_url` — Read — https://policylayer.com/tools/a1official-mcp/redmine-oauth-get-auth-url.md
- `redmine_oauth_list_issues` — Read — https://policylayer.com/tools/a1official-mcp/redmine-oauth-list-issues.md
- `redmine_oauth_list_projects` — Read — https://policylayer.com/tools/a1official-mcp/redmine-oauth-list-projects.md
- `redmine_quality_metrics` — Read — https://policylayer.com/tools/a1official-mcp/redmine-quality-metrics.md
- `redmine_release_status` — Read — https://policylayer.com/tools/a1official-mcp/redmine-release-status.md
- `redmine_sprint_analytics` — Read — https://policylayer.com/tools/a1official-mcp/redmine-sprint-analytics.md
- `redmine_team_workload` — Read — https://policylayer.com/tools/a1official-mcp/redmine-team-workload.md
- `redmine_throughput` — Read — https://policylayer.com/tools/a1official-mcp/redmine-throughput.md
- `redmine_velocity_trend` — Read — https://policylayer.com/tools/a1official-mcp/redmine-velocity-trend.md
- `scrape_products` — Read — https://policylayer.com/tools/a1official-mcp/scrape-products.md
- `search_duckduckgo` — Read — https://policylayer.com/tools/a1official-mcp/search-duckduckgo.md
- `search_google` — Read — https://policylayer.com/tools/a1official-mcp/search-google.md
- `search_music` — Read — https://policylayer.com/tools/a1official-mcp/search-music.md
- `search_products_smart` — Read — https://policylayer.com/tools/a1official-mcp/search-products-smart.md
- `redmine_create_issue` — Write — https://policylayer.com/tools/a1official-mcp/redmine-create-issue.md
- …and 2 more: https://policylayer.com/tools/a1official-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a1official-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a1official-mcp