Schedule a new post for future publishing.
AI agents use schedule_post to create or update resources in Just Facebook MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Just Facebook MCP Server environment.
This tool creates new data (a scheduled post) reversibly. While the post will be published automatically, scheduling is a Write operation: the action is reversible before publication (the scheduled post can be cancelled/deleted), and it doesn't execute arbitrary code or delete data.
From the tool's definition Tool description states 'Schedule a new post for future publishing' — this creates new content on Facebook that will be published, modifying the Page's content feed.
Documented attack patterns abuse exactly the kind of access schedule_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Just Facebook MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for schedule_post:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_post": {
"limits": [
{
"counter": "schedule_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} schedule_post 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.
Free to start. No card required.
Schedule a new post for future publishing. It is categorised as a Write tool in the Just Facebook MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Just Facebook MCP Server MCP server in PolicyLayer and add a rule for schedule_post: 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 Just Facebook MCP Server. Nothing to install.
schedule_post 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 schedule_post 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 schedule_post. 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.
schedule_post is provided by the Just Facebook MCP Server MCP server (livia-zaharia/just_facebook_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Just Facebook MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 Just Facebook MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.