list_portfolio_snapshot_notes
Read the decision and comment thread recorded against one of your portfolio snapshots, oldest first. Each note carries the snapshot content hash it was written against plus binding_intact comparing that hash to the snapshot's hash now, so a note can be read as evidence of what was actually on the...
This record as markdown: /tools/com-meta-council-decision-intelligence/list-portfolio-snapshot-notes.md
What list_portfolio_snapshot_notes does on Meta Council
AI agents call list_portfolio_snapshot_notes 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 notes to return. Defaults to 100. |
snapshot_id | string | Yes | The snapshot's id, from list_portfolio_snapshots. |
after_note_id | string | — | Continue after this note in the same owned snapshot, using next_after_id. |
Parameters from the server's own tool schema.
Why list_portfolio_snapshot_notes is rated Low
Even though list_portfolio_snapshot_notes 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_snapshot_notes 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_snapshot_notes, this is the rule to start with:
list_portfolio_snapshot_notes 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_snapshot_notes call is checked against it from then on.
Questions about list_portfolio_snapshot_notes
Read the decision and comment thread recorded against one of your portfolio snapshots, oldest first. Each note carries the snapshot content hash it was written against plus binding_intact comparing that hash to the snapshot's hash now, so a note can be read as evidence of what was actually on the screen when it was written. Counts are over the notes actually returned, so a truncated page never reports a total it did not show. Continue with next_after_id as after_note_id when has_more is true. New notes can arrive between pages; restart to refresh the thread. This reads the thread; it does not approve, reject or block anything. 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_snapshot_notes accepts 3 parameters: limit, snapshot_id, after_note_id. Required: snapshot_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_snapshot_notes: 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_snapshot_notes 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_snapshot_notes 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_snapshot_notes. 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_snapshot_notes 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