run_weekly_schedule_day

A execute tool on the Postking MCP server.

SERVERPostking Mcp SOURCEpostking-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/run-weekly-schedule-day.md

What run_weekly_schedule_day does on Postking Mcp

AI agents invoke run_weekly_schedule_day to trigger actions in Postking Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why run_weekly_schedule_day is rated High

Although the description is empty, the tool name and server context suggest this executes a predetermined workflow that publishes or schedules content. This is Execute-category because it triggers external operations (post publication, content scheduling) whose effects are determined by prior configuration.

From the tool's definition Tool name 'run_weekly_schedule_day' indicates execution of a scheduled workflow. Context shows this is a content scheduling/publishing server where running schedules would trigger posting actions across platforms.

Questions about run_weekly_schedule_day

What does the run_weekly_schedule_day tool do? +

run_weekly_schedule_day is a execute tool on the Postking MCP server. It is categorised as a Execute tool in the Postking Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_weekly_schedule_day? +

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

run_weekly_schedule_day is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_weekly_schedule_day? +

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

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

run_weekly_schedule_day 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.

More on Postking, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Postking's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.