# gradle-tasks

Lists available Gradle tasks with descriptions and groups. Uses

Agent View of the PolicyLayer registry record for `gradle-tasks`. HTML page: https://policylayer.com/tools/io-github-dave-london-http/gradle-tasks

## Facts

- Tool: `gradle-tasks`
- Server: Http (`@paretools/http`) — https://policylayer.com/tools/io-github-dave-london-http.md
- Install: `npx -y @paretools/http`
- Homepage: https://github.com/Dave-London/Pare
- 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": "gradle-tasks",
    "arguments": {}
  }
}
```

## Why gradle-tasks is rated Low

This tool retrieves information about available Gradle tasks in a project. It performs a read-only operation that queries the Gradle build system for metadata about tasks, their descriptions, and groupings. There is no modification, execution of arbitrary commands, deletion, or financial impact. The tool is informational and safe for AI agents to use.

From the tool's own definition: "Tool name 'gradle-tasks' and description 'Lists available Gradle tasks with descriptions and groups' indicates a query/retrieval operation with no side effects."

## Use case

AI agents call gradle-tasks to retrieve information from Http 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 Http:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gradle-tasks": {}
  }
}
```

## Other tools on Http (201)

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