get_calendar

View upcoming scheduled posts sorted by date. Returns id+status+scheduledAt by default; use detail=

SERVERPostking Mcp SOURCEpostking-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/get-calendar.md

WHAT IT DOES

What get_calendar does on Postking Mcp

AI agents call get_calendar to retrieve information from Postking Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_calendar is rated Low

This tool queries and returns existing scheduled post metadata without causing any side effects. It retrieves information about previously created posts (id, status, scheduledAt), which is a data retrieval operation characteristic of the Read category. No data is created, modified, deleted, or executed.

From the tool's definition The tool 'get_calendar' is described as 'View upcoming scheduled posts sorted by date. Returns id+status+scheduledAt by default' — these are read-only retrieval operations with no modification, deletion, or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_calendar safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_calendar, this is the rule to start with:

get_calendar Allowed

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

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

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

FAQ

Questions about get_calendar

What does the get_calendar tool do? +

View upcoming scheduled posts sorted by date. Returns id+status+scheduledAt by default; use detail=. It is categorised as a Read tool in the Postking Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_calendar? +

Register the Postking MCP server in PolicyLayer and add a rule for get_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 Postking Mcp. Nothing to install.

What risk level is get_calendar? +

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

Can I rate-limit get_calendar? +

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

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

get_calendar is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What get_calendar does on Postking Mcp

Why get_calendar is rated Low

The rule that runs get_calendar safely

Questions about get_calendar

More on Postking, and thousands of servers like it.