create_saved_view
Save a named ticket filter, column, grouping and sort bundle so you can reopen it later or share it with a team. Saves the QUESTION, not an answer: the view is re-run against live tickets every time it is opened, so it never goes stale. The new view is private until you share it. Same endpoint th...
This record as markdown: /tools/com-meta-council-decision-intelligence/create-saved-view.md
What create_saved_view does on Meta Council
AI agents use create_saved_view to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | What to call the view. |
columns | array | Yes | Which ticket columns the view shows, in order. At most 20. |
filters | object | — | Saved question. Omitted reader selects ordinary tickets. Attention accepts reason; reviewed_attention accepts state and follow_up. Triage refuses other non-defa |
sort_by | string | — | Optional ticket field to sort rows by. |
group_by | string | — | Optional ticket field to group rows by. |
sort_dir | string | — | Sort direction. Defaults to asc. |
scorecard | object | null | — | Optional private ordinary live ticket counts; omit to retain, null to clear while retaining a nonzero revision. At most 10000 matching tickets, no actions or ro |
expected_revision | integer | — | Current definition_revision, required to configure a scorecard or change any previously enrolled view. On conflict or uncertain reply, read current state and de |
Parameters from the server's own tool schema.
Why create_saved_view is rated Medium
An AI agent can call create_saved_view faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (23 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs create_saved_view 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 create_saved_view, this is the rule to start with:
create_saved_view stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_saved_view call is checked against it from then on.
Questions about create_saved_view
Save a named ticket filter, column, grouping and sort bundle so you can reopen it later or share it with a team. Saves the QUESTION, not an answer: the view is re-run against live tickets every time it is opened, so it never goes stale. The new view is private until you share it. Same endpoint the web app's save button uses. Requires authentication and the tickets:write scope. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_saved_view accepts 8 parameters: name, columns, filters, sort_by, group_by, sort_dir, scorecard, expected_revision. Required: name, columns. 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 create_saved_view: 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.
create_saved_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_saved_view 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 create_saved_view. 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.
create_saved_view 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