update_portfolio_schedule

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

Medium RISK CLASS

Category Write

Parameters 44 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/update-portfolio-schedule.md

WHAT IT DOES

What update_portfolio_schedule does on Meta Council

AI agents use update_portfolio_schedule 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
`definition`	object	Yes
`request_id`	string	Yes
`schedule_id`	string	Yes
`expected_revision`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why update_portfolio_schedule is rated Medium

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

Risk signalsHigh parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_portfolio_schedule Rate-limited

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

FAQ

Questions about update_portfolio_schedule

What does the update_portfolio_schedule tool do? +

Replace the full definition of an owned report schedule using its current expected_revision. Preserve project_id from project_list when retaining project scope; omission or null selects portfolio scope. Pause with enabled=false; archive also disables, and restore paused. Editing an enabled schedule starts at its next future occurrence. Reuse the exact request_id and request for recovery; an exact retry returns the original receipt, so read current state afterward. Requires 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 update_portfolio_schedule accept? +

update_portfolio_schedule accepts 4 parameters: definition, request_id, schedule_id, expected_revision. Required: definition, request_id, schedule_id, expected_revision. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_portfolio_schedule? +

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

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

Can I rate-limit update_portfolio_schedule? +

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

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

update_portfolio_schedule 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

sms_schedule on Twilio SMS MCP Server →aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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