# aroflo_resolve_job_context

Resolve a job context (jobnumber + related task(s), quote(s), and project) starting from any of: jobNumber, quoteId, quoteRefno, projectId, or projectRefno.

Agent View of the PolicyLayer registry record for `aroflo_resolve_job_context`. HTML page: https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-resolve-job-context

## Facts

- Tool: `aroflo_resolve_job_context`
- 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_resolve_job_context",
    "arguments": {}
  }
}
```

## Why aroflo_resolve_job_context is rated Low

The tool resolves/fetches contextual information about a job given various identifiers. It queries and returns data (job number, tasks, quotes, project) with no indication of creating, modifying, or deleting anything. This is a pure read/lookup operation.

From the tool's own definition: "'Resolve a job context' starting from identifiers — retrieves related tasks, quotes, and project data without any modification"

## Use case

AI agents call aroflo_resolve_job_context 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_resolve_job_context": {}
  }
}
```

## 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_open_projects` — Read — https://policylayer.com/tools/0x1notme-aroflo-mcp/aroflo-list-open-projects.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_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