get_content_calendar

List scheduled owned content between optional ISO-8601 boundaries. Scheduling is planning metadata, not publishing.

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

Low RISK CLASS

Category Read

Parameters 20 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/get-content-calendar.md

WHAT IT DOES

What get_content_calendar does on Meta Council

AI agents call get_content_calendar 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	Description
`end`	string	—
`start`	string	—

Parameters from the server's own tool schema.

RISK

Why get_content_calendar is rated Low

This tool retrieves and queries scheduling metadata for owned content within optional date boundaries. It has no modifying, executing, deleting, or financial effects. It is a straightforward read operation with minimal risk.

From the tool's definition Tool name is 'get_content_calendar' and description states 'List scheduled owned content' — verb is 'list', a retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_content_calendar Allowed

get_content_calendar 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": {
    "get_content_calendar": {}
  }
}

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 get_content_calendar call is checked against it from then on.

FAQ

Questions about get_content_calendar

What does the get_content_calendar tool do? +

List scheduled owned content between optional ISO-8601 boundaries. Scheduling is planning metadata, not publishing. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

What parameters does get_content_calendar accept? +

get_content_calendar accepts 2 parameters: end, start. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_content_calendar? +

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

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

Can I rate-limit get_content_calendar? +

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

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

get_content_calendar 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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