share_saved_view
Share one of YOUR OWN saved views with a single team you belong to. Members may read, list and execute it; only you may revise, re-share or delete it. Executing a shared view runs it against the READER's own tickets, so this shares the question and never the answers. Re-sharing to a different tea...
This record as markdown: /tools/com-meta-council-decision-intelligence/share-saved-view.md
What share_saved_view does on Meta Council
AI agents call share_saved_view 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 |
|---|---|---|---|
team_id | string | Yes | The id of a team you belong to. Sharing with a team you are not a member of is refused. |
view_id | string | Yes | The view's id, from list_saved_views. |
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 share_saved_view is rated Low
Even though share_saved_view 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 share_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 share_saved_view, this is the rule to start with:
share_saved_view 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 share_saved_view call is checked against it from then on.
Questions about share_saved_view
Share one of YOUR OWN saved views with a single team you belong to. Members may read, list and execute it; only you may revise, re-share or delete it. Executing a shared view runs it against the READER's own tickets, so this shares the question and never the answers. Re-sharing to a different team MOVES the view rather than adding a second grant -- a view is readable by at most one team. Note: team ids are not currently discoverable from this MCP surface, so supply one you already hold. Requires authentication and the tickets:write scope. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
share_saved_view accepts 3 parameters: team_id, view_id, expected_revision. Required: team_id, view_id. 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 share_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.
share_saved_view 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 share_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 share_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.
share_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