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...
This record as markdown: /tools/com-meta-council-decision-intelligence/get-ticket-attention-queue.md
What get_ticket_attention_queue does on Meta Council
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
offset | integer | — | |
reason | string | — |
Parameters from the server's own tool schema.
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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_ticket_attention_queue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_ticket_attention_queue, this is the rule to start with:
get_ticket_attention_queue is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every get_ticket_attention_queue call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_ticket_attention_queue accepts 3 parameters: limit, offset, reason. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for get_ticket_attention_queue: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Meta Council. Nothing to install.
get_ticket_attention_queue is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_ticket_attention_queue rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_ticket_attention_queue. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_ticket_attention_queue is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue