# get_ticket_attention_queue

Read the same ranked Needs attention queue as the browser and REST. Returns complete JSON with reasons, UTC clock evidence, effective owner policy thresholds and revision, approximation flags, unmet prerequisites and suggested next actions. Open active owned tickets only; limit 1–500 (default 100), offset 0–2147483647 (default 0). Continue with next_offset when has_more; refresh at offset 0. Membership/rank can shift between live pages. total_flagged/truncated disclose partial coverage. Filter reason before the limit, including missed_due_date with saved date/timezone/calendar/version after its entire local day. Weekends and status pauses never extend commitments; age is elapsed 24-hour days. Completion blockers have no age or threshold. Blocked work with unproven history remains visible with an unknown age and its configured threshold. Ranked by greatest known days over threshold, then ticket UUID; items with no elapsed clock sort last. No state changes, acknowledgments, notifications or provider calls. Requires tickets:read.

Agent View of the PolicyLayer registry record for `get_ticket_attention_queue`. HTML page: https://policylayer.com/tools/com-meta-council-decision-intelligence/get-ticket-attention-queue

## Facts

- Tool: `get_ticket_attention_queue`
- Server: Meta Council (`https://meta-council.com/mcp`) — https://policylayer.com/tools/com-meta-council-decision-intelligence.md
- Homepage: https://github.com/daliu/meta-council
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no |  |
| `offset` | integer | no |  |
| `reason` | string | no |  |

Parameters from the server's own tool schema.

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

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

## Why get_ticket_attention_queue is rated Low

Even though get_ticket_attention_queue only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call get_ticket_attention_queue to retrieve information from Meta Council 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 Meta Council:

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

## Other tools on Meta Council (279)

- `account_export` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/account-export.md
- `cancel_booking` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/cancel-booking.md
- `decide_approval` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/decide-approval.md
- `delete_accounting_run` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/delete-accounting-run.md
- `delete_monitor` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/delete-monitor.md
- `delete_saved_view` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/delete-saved-view.md
- `delete_workflow_template` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/delete-workflow-template.md
- `preview_scheduling_action` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/preview-scheduling-action.md
- `project_unlink_feature` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/project-unlink-feature.md
- `reconcile_attention_notification_delivery` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/reconcile-attention-notification-delivery.md
- `revoke_portfolio_report_share` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/revoke-portfolio-report-share.md
- `ticket_dependency_remove` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/ticket-dependency-remove.md
- `void_invoice` — Destructive — https://policylayer.com/tools/com-meta-council-decision-intelligence/void-invoice.md
- `dismiss_ticket_integration_effect` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/dismiss-ticket-integration-effect.md
- `execute_saved_view` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/execute-saved-view.md
- `preview_accounting_ticket_sync` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/preview-accounting-ticket-sync.md
- `project_link_feature` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/project-link-feature.md
- `retry_workflow` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/retry-workflow.md
- `review_external_workflow` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/review-external-workflow.md
- `run_comparison` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/run-comparison.md
- `run_council` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/run-council.md
- `run_workflow` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/run-workflow.md
- `start_external_workflow` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/start-external-workflow.md
- `ticket_scenario_revise` — Execute — https://policylayer.com/tools/com-meta-council-decision-intelligence/ticket-scenario-revise.md
- `add_invoice_line_item` — Financial — https://policylayer.com/tools/com-meta-council-decision-intelligence/add-invoice-line-item.md
- `mark_invoice_paid` — Financial — https://policylayer.com/tools/com-meta-council-decision-intelligence/mark-invoice-paid.md
- `advance_workflow` — Read — https://policylayer.com/tools/com-meta-council-decision-intelligence/advance-workflow.md
- `ask_legal` — Read — https://policylayer.com/tools/com-meta-council-decision-intelligence/ask-legal.md
- `browse_ticket_integration_import` — Read — https://policylayer.com/tools/com-meta-council-decision-intelligence/browse-ticket-integration-import.md
- `campaign_pipeline_stats` — Read — https://policylayer.com/tools/com-meta-council-decision-intelligence/campaign-pipeline-stats.md
- …and 249 more: https://policylayer.com/tools/com-meta-council-decision-intelligence.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=com-meta-council-decision-intelligence · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-meta-council-decision-intelligence