# claudeus_plane_issues__get

Gets a single issue by ID from a Plane project

Agent View of the PolicyLayer registry record for `claudeus_plane_issues__get`. HTML page: https://policylayer.com/tools/deus-h-claudeus-plane-mcp/claudeus-plane-issues--get

## Facts

- Tool: `claudeus_plane_issues__get`
- Server: Claudeus Plane MCP (`deus-h/claudeus-plane-mcp`) — https://policylayer.com/tools/deus-h-claudeus-plane-mcp.md
- Homepage: https://github.com/deus-h/claudeus-plane-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, 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": "claudeus_plane_issues__get",
    "arguments": {}
  }
}
```

## Why claudeus_plane_issues__get is rated Low

This tool retrieves data (a single issue) without modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent.

From the tool's own definition: "Tool name contains 'get' and description states 'Gets a single issue by ID from a Plane project' — a retrieval operation with no side effects."

## Use case

AI agents call claudeus_plane_issues__get to retrieve information from Claudeus Plane MCP 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 Claudeus Plane MCP:

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

## Other tools on Claudeus Plane MCP (7)

- `claudeus_plane_projects__delete` — Destructive — https://policylayer.com/tools/deus-h-claudeus-plane-mcp/claudeus-plane-projects--delete.md
- `claudeus_plane_issues__list` — Read — https://policylayer.com/tools/deus-h-claudeus-plane-mcp/claudeus-plane-issues--list.md
- `claudeus_plane_projects__list` — Read — https://policylayer.com/tools/deus-h-claudeus-plane-mcp/claudeus-plane-projects--list.md
- `claudeus_plane_issues__create` — Write — https://policylayer.com/tools/deus-h-claudeus-plane-mcp/claudeus-plane-issues--create.md
- `claudeus_plane_issues__update` — Write — https://policylayer.com/tools/deus-h-claudeus-plane-mcp/claudeus-plane-issues--update.md
- `claudeus_plane_projects__create` — Write — https://policylayer.com/tools/deus-h-claudeus-plane-mcp/claudeus-plane-projects--create.md
- `claudeus_plane_projects__update` — Write — https://policylayer.com/tools/deus-h-claudeus-plane-mcp/claudeus-plane-projects--update.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=deus-h-claudeus-plane-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deus-h-claudeus-plane-mcp