list_saved_views
List saved ticket views you can open: the stored filter, column, grouping and sort combinations saved by you, plus any shared with a team you belong to. Shared views appear under the active and all scopes and never once archived, because an owner's archive is their own working state. Returns the ...
This record as markdown: /tools/com-meta-council-decision-intelligence/list-saved-views.md
What list_saved_views does on Meta Council
AI agents call list_saved_views 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 | — | How many views per page. Defaults to 50. |
scope | string | — | Which of YOUR OWN views to include: active (the default, excluding archived), archived (your recovery list), or all. Shared views are unaffected by archived and |
cursor | string | — | Opaque next_cursor from the same caller and scope; expires after 24 hours. Omit to refresh. |
Parameters from the server's own tool schema.
Why list_saved_views is rated Low
Even though list_saved_views 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 list_saved_views 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_saved_views, this is the rule to start with:
list_saved_views 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_saved_views call is checked against it from then on.
Questions about list_saved_views
List saved ticket views you can open: the stored filter, column, grouping and sort combinations saved by you, plus any shared with a team you belong to. Shared views appear under the active and all scopes and never once archived, because an owner's archive is their own working state. Returns the same payload the web app's saved-view list returns. Requires authentication and the tickets:read scope. Pages use immutable creation-time/ID order; follow next_cursor while has_more. Current permissions and archive state are rechecked on every page; this is live metadata. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
list_saved_views accepts 3 parameters: limit, scope, cursor. 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_saved_views: 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_saved_views 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_saved_views 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_saved_views. 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_saved_views 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