# issue-create

Creates a new issue. Returns structured data with issue number, URL, and labels applied.

Agent View of the PolicyLayer registry record for `issue-create`. HTML page: https://policylayer.com/tools/io-github-dave-london-git/issue-create

## Facts

- Tool: `issue-create`
- Server: Git (`Dave-London/Pare`) — https://policylayer.com/tools/io-github-dave-london-git.md
- Homepage: https://github.com/Dave-London/pare
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why issue-create is rated Medium

This tool creates new issues in a git/repository system, which is a reversible write operation. Issues can typically be deleted or closed, so it does not rise to Destructive. The severity is medium because malicious creation of many issues could disrupt project management and waste maintainer time, but does not directly compromise code integrity, financial systems, or trigger external operations.

From the tool's own definition: "Tool name 'issue-create' and description 'Creates a new issue' indicate creation of new data. Returns issue number, URL, and labels, confirming persistent data modification."

## Use case

AI agents use issue-create to create or update resources in Git, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Git:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "issue-create": {
      "limits": [
        {
          "counter": "issue-create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Git (201)

- `branch` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/branch.md
- `clean` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/clean.md
- `package-clean` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/package-clean.md
- `remove` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/remove.md
- `reset` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/reset.md
- `secret-delete` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/secret-delete.md
- `stash` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/stash.md
- `tag` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/tag.md
- `variable-delete` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/variable-delete.md
- `workspace` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/workspace.md
- `worktree` — Destructive — https://policylayer.com/tools/io-github-dave-london-git/worktree.md
- `add-package` — Execute — https://policylayer.com/tools/io-github-dave-london-git/add-package.md
- `ansible-galaxy` — Execute — https://policylayer.com/tools/io-github-dave-london-git/ansible-galaxy.md
- `ansible-playbook` — Execute — https://policylayer.com/tools/io-github-dave-london-git/ansible-playbook.md
- `api` — Execute — https://policylayer.com/tools/io-github-dave-london-git/api.md
- `apply` — Execute — https://policylayer.com/tools/io-github-dave-london-git/apply.md
- `audit` — Execute — https://policylayer.com/tools/io-github-dave-london-git/audit.md
- `bazel` — Execute — https://policylayer.com/tools/io-github-dave-london-git/bazel.md
- `bisect` — Execute — https://policylayer.com/tools/io-github-dave-london-git/bisect.md
- `black` — Execute — https://policylayer.com/tools/io-github-dave-london-git/black.md
- `build` — Execute — https://policylayer.com/tools/io-github-dave-london-git/build.md
- `bundle-exec` — Execute — https://policylayer.com/tools/io-github-dave-london-git/bundle-exec.md
- `bundle-install` — Execute — https://policylayer.com/tools/io-github-dave-london-git/bundle-install.md
- `check` — Execute — https://policylayer.com/tools/io-github-dave-london-git/check.md
- `checkout` — Execute — https://policylayer.com/tools/io-github-dave-london-git/checkout.md
- `cherry-pick` — Execute — https://policylayer.com/tools/io-github-dave-london-git/cherry-pick.md
- `clippy` — Execute — https://policylayer.com/tools/io-github-dave-london-git/clippy.md
- `cmake` — Execute — https://policylayer.com/tools/io-github-dave-london-git/cmake.md
- `compose-build` — Execute — https://policylayer.com/tools/io-github-dave-london-git/compose-build.md
- `compose-down` — Execute — https://policylayer.com/tools/io-github-dave-london-git/compose-down.md
- …and 171 more: https://policylayer.com/tools/io-github-dave-london-git.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=io-github-dave-london-git · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-dave-london-git