list_reviewed_attention
Discover latest owned attention reviews, including cleared, terminal, archived and unavailable work. Requires tickets:read. Filter unresolved (including withdrawn), resolved or all; independently set follow_up=due for saved follow-ups whose stored UTC instant has arrived. Due pages sort oldest fi...
This record as markdown: /tools/com-meta-council-decision-intelligence/list-reviewed-attention.md
What list_reviewed_attention does on Meta Council
AI agents call list_reviewed_attention 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 | — | |
state | string | — | |
cursor | string | — | |
follow_up | string | — |
Parameters from the server's own tool schema.
Why list_reviewed_attention is rated Low
Even though list_reviewed_attention 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.
Attacks that exploit this kind of access
The rule that runs list_reviewed_attention 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 list_reviewed_attention, this is the rule to start with:
list_reviewed_attention 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 list_reviewed_attention call is checked against it from then on.
Questions about list_reviewed_attention
Discover latest owned attention reviews, including cleared, terminal, archived and unavailable work. Requires tickets:read. Filter unresolved (including withdrawn), resolved or all; independently set follow_up=due for saved follow-ups whose stored UTC instant has arrived. Due pages sort oldest first and retain their cutoff; refresh without a cursor for newly due work. Latest-review and declaration membership remain live. limit 1–50, owner/filter-bound cursor. Current ticket metadata is separate from retained reviewed evidence. No queue filtering or providers. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
list_reviewed_attention accepts 4 parameters: limit, state, cursor, follow_up. 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 list_reviewed_attention: 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.
list_reviewed_attention 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 list_reviewed_attention 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 list_reviewed_attention. 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.
list_reviewed_attention 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