export_portfolio_snapshot
Download one owned saved report using the same JSON, CSV, accessible HTML or optional tagged PDF renderer as the browser. Returns filename, media_type, encoding, content and SHA-256; PDF content is base64. Unsupported PDF fonts or renderer dependencies return an explicit error with HTML fallback....
This record as markdown: /tools/com-meta-council-decision-intelligence/export-portfolio-snapshot.md
What export_portfolio_snapshot does on Meta Council
AI agents use export_portfolio_snapshot 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 |
|---|---|---|---|
format | string | — | |
snapshot_id | string | Yes |
Parameters from the server's own tool schema.
Why export_portfolio_snapshot is rated Medium
An AI agent can call export_portfolio_snapshot 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.
Attacks that exploit this kind of access
The rule that runs export_portfolio_snapshot 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 export_portfolio_snapshot, this is the rule to start with:
export_portfolio_snapshot 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 export_portfolio_snapshot call is checked against it from then on.
Questions about export_portfolio_snapshot
Download one owned saved report using the same JSON, CSV, accessible HTML or optional tagged PDF renderer as the browser. Returns filename, media_type, encoding, content and SHA-256; PDF content is base64. Unsupported PDF fonts or renderer dependencies return an explicit error with HTML fallback. No network delivery or share link is created. Requires tickets:read. 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.
export_portfolio_snapshot accepts 2 parameters: format, snapshot_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 export_portfolio_snapshot: 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.
export_portfolio_snapshot 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 export_portfolio_snapshot 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 export_portfolio_snapshot. 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.
export_portfolio_snapshot 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