# aroflo_list_open_projects

List open projects with optional client-side filtering (status/open + closeddate empty).

Agent View of the PolicyLayer registry record for `aroflo_list_open_projects`. HTML page: https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-list-open-projects

## Facts

- Tool: `aroflo_list_open_projects`
- Server: AroFlo MCP (`0x1notme/aroflo-mcp`) — https://policylayer.com/tools/0x1notme-aroflo-mcp.md
- Homepage: https://github.com/0x1NotMe/aroflo-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, 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": "aroflo_list_open_projects",
    "arguments": {}
  }
}
```

## Why aroflo_list_open_projects is rated Low

This tool retrieves and filters project data without creating, modifying, deleting, or executing operations. It has minimal blast radius—an AI agent misusing it would at worst retrieve unwanted project information, but cannot cause data loss or financial harm. Classified as Read with low severity.

From the tool's own definition: "Tool name 'list_open_projects' and description 'List open projects with optional client-side filtering' indicate data retrieval with no modification. The filtering is described as 'client-side', confirming query-only behavior."

## Use case

AI agents call aroflo_list_open_projects to retrieve information from AroFlo 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 AroFlo MCP:

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

## Other tools on AroFlo MCP (8)

- `aroflo_query_zone` — Execute — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-query-zone.md
- `aroflo_get_lastupdate` — Read — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-get-lastupdate.md
- `aroflo_get_record` — Read — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-get-record.md
- `aroflo_list_project_tasks_with_hours` — Read — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-list-project-tasks-with-hours.md
- `aroflo_report_open_projects_with_task_hours` — Read — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-report-open-projects-with-task-hours.md
- `aroflo_report_project_labour_budget_audit` — Read — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-report-project-labour-budget-audit.md
- `aroflo_resolve_job_context` — Read — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-resolve-job-context.md
- `aroflo_create_or_update_record` — Write — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-create-or-update-record.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=0x1notme-aroflo-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0x1notme-aroflo-mcp