create_portfolio_schedule
Create an owner-private daily, weekly or monthly portfolio report schedule. Defaults to paused; explicitly enable to start internal captures. Uses the same active-ticket aggregate as manual reports. Optional project_id from project_list limits captures to that owned project; each report retains i...
This record as markdown: /tools/com-meta-council-decision-intelligence/create-portfolio-schedule.md
What create_portfolio_schedule does on Meta Council
AI agents use create_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 | Description |
|---|---|---|---|
definition | object | Yes | |
request_id | string | Yes |
Parameters from the server's own tool schema.
Why create_portfolio_schedule is rated Medium
An AI agent can call create_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 (12 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_portfolio_schedule, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every create_portfolio_schedule call is checked against it from then on.
Questions about create_portfolio_schedule
Create an owner-private daily, weekly or monthly portfolio report schedule. Defaults to paused; explicitly enable to start internal captures. Uses the same active-ticket aggregate as manual reports. Optional project_id from project_list limits captures to that owned project; each report retains its own inputs. No email or provider calls. Preserve request_id and exact intent when retrying an uncertain reply. 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.
create_portfolio_schedule accepts 2 parameters: definition, request_id. Required: definition, request_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 create_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.
create_portfolio_schedule 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue