list_portfolio_snapshots
List your own portfolio (default), project or all snapshots, newest first. Project scope requires project_id: the immutable rollups of how your ticket portfolio stood at the moments you captured them. Each carries its label, schema version, stored payload, content hash, recording actor and creati...
This record as markdown: /tools/com-meta-council-decision-intelligence/list-portfolio-snapshots.md
What list_portfolio_snapshots does on Meta Council
AI agents call list_portfolio_snapshots 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 snapshots to return. Defaults to 50. |
scope | string | — | |
project_id | string | — |
Parameters from the server's own tool schema.
Why list_portfolio_snapshots is rated Low
Even though list_portfolio_snapshots 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_portfolio_snapshots 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_portfolio_snapshots, this is the rule to start with:
list_portfolio_snapshots 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_portfolio_snapshots call is checked against it from then on.
Questions about list_portfolio_snapshots
List your own portfolio (default), project or all snapshots, newest first. Project scope requires project_id: the immutable rollups of how your ticket portfolio stood at the moments you captured them. Each carries its label, schema version, stored payload, content hash, recording actor and creation time. Snapshots are owner-private and never span accounts. Returns the same payload the web app's snapshot list returns. Requires authentication and the tickets:read scope. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
list_portfolio_snapshots accepts 3 parameters: limit, scope, project_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 list_portfolio_snapshots: 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_portfolio_snapshots 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_portfolio_snapshots 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_portfolio_snapshots. 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_portfolio_snapshots 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