supersede_portfolio_report

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

Medium RISK CLASS

Category Write

Parameters 66 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/supersede-portfolio-report.md

WHAT IT DOES

What supersede_portfolio_report does on Meta Council

AI agents use supersede_portfolio_report 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
`reason`	string	Yes
`snapshot_id`	string	Yes
`replacement_id`	string	Yes
`idempotency_key`	string	Yes
`expected_source_hash`	string	Yes
`expected_replacement_hash`	string	Yes

Parameters from the server's own tool schema.

RISK

Why supersede_portfolio_report is rated Medium

An AI agent can call supersede_portfolio_report 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 supersede_portfolio_report 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 supersede_portfolio_report, this is the rule to start with:

supersede_portfolio_report Rate-limited

supersede_portfolio_report 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": {
    "supersede_portfolio_report": {
      "limits": [
        {
          "counter": "supersede_portfolio_report_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 supersede_portfolio_report call is checked against it from then on.

FAQ

Questions about supersede_portfolio_report

What does the supersede_portfolio_report tool do? +

Record that one owned saved report replaces another, with a required reason and both fetched payload hashes. This is an immutable owner declaration, not approval, sharing or a claim of accuracy. Both reports must have no replacement recorded. Use the same key and exact payload after an uncertain response; exact retries return the original receipt even after later replacements. Conflicting keys, self-links and cycles are refused. Original exports stay unchanged. tickets:write. 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 supersede_portfolio_report accept? +

supersede_portfolio_report accepts 6 parameters: reason, snapshot_id, replacement_id, idempotency_key, expected_source_hash, expected_replacement_hash. Required: reason, snapshot_id, replacement_id, idempotency_key, expected_source_hash, expected_replacement_hash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on supersede_portfolio_report? +

Register the Meta Council MCP server in PolicyLayer and add a rule for supersede_portfolio_report: 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 supersede_portfolio_report? +

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

Can I rate-limit supersede_portfolio_report? +

Yes. Add a rate_limit block to the supersede_portfolio_report 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 supersede_portfolio_report completely? +

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

supersede_portfolio_report 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

generate_devtools_report on Percepta MCP Server →generate_forensic_report on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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