create_portfolio_snapshot

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/create-portfolio-snapshot.md

WHAT IT DOES

What create_portfolio_snapshot does on Meta Council

AI agents use create_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
`label`	string	—	Optional human label, e.g. the review it was taken for. Omitted leaves the snapshot unlabelled.
`project_id`	string	—	Owned ProjectWorkspace UUID from project_list. Omit for the whole portfolio.
`request_id`	string	—	Reuse this UUID and the exact label/project scope to recover an uncertain capture.

Parameters from the server's own tool schema.

RISK

Why create_portfolio_snapshot is rated Medium

An AI agent can call create_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

RECOMMENDED RULE

The rule that runs create_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 create_portfolio_snapshot, this is the rule to start with:

create_portfolio_snapshot Rate-limited

create_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_portfolio_snapshot": {
      "limits": [
        {
          "counter": "create_portfolio_snapshot_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every create_portfolio_snapshot call is checked against it from then on.

FAQ

Questions about create_portfolio_snapshot

What does the create_portfolio_snapshot tool do? +

Capture an immutable rollup of YOUR OWN ticket portfolio, or one owned ProjectWorkspace when project_id is supplied, as it stands right now -- totals by status and priority, fixed at this moment and never recomputed. A snapshot is the durable 'here is where we were' that a later diff_portfolio_snapshots measures movement against, so capture one before a review rather than after. Snapshots cannot be edited or deleted once taken. The snapshot records the credential that captured it, so one taken by an agent is attributable as such. 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.

What parameters does create_portfolio_snapshot accept? +

create_portfolio_snapshot accepts 3 parameters: label, project_id, request_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_portfolio_snapshot? +

Register the Meta Council MCP server in PolicyLayer and add a rule for create_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.

What risk level is create_portfolio_snapshot? +

create_portfolio_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_portfolio_snapshot? +

Yes. Add a rate_limit block to the create_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.

How do I block create_portfolio_snapshot completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_portfolio_snapshot? +

create_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.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →