list_portfolio_schedule_revisions

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

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/list-portfolio-schedule-revisions.md

WHAT IT DOES

What list_portfolio_schedule_revisions does on Meta Council

AI agents call list_portfolio_schedule_revisions 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
`limit`	integer	—
`schedule_id`	string	Yes
`before_revision`	integer	—

Parameters from the server's own tool schema.

RISK

Why list_portfolio_schedule_revisions is rated Low

Even though list_portfolio_schedule_revisions 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

RECOMMENDED RULE

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

list_portfolio_schedule_revisions Allowed

list_portfolio_schedule_revisions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_portfolio_schedule_revisions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_portfolio_schedule_revisions

What does the list_portfolio_schedule_revisions tool do? +

Read immutable definition revisions of one owned report schedule, including paused or archived schedules. Newest revision first; follow next_before_revision while has_more. No capture or state change. Requires tickets:read. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

What parameters does list_portfolio_schedule_revisions accept? +

list_portfolio_schedule_revisions accepts 3 parameters: limit, schedule_id, before_revision. Required: schedule_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_portfolio_schedule_revisions? +

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

list_portfolio_schedule_revisions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_portfolio_schedule_revisions? +

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

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

list_portfolio_schedule_revisions 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

list_symbols on ACE-MCP →aiva_get_delivery_schedule on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →