Schedule a post to be published at a future time. The scheduled_time must be between 10 minutes and 75 days from now (Unix timestamp in seconds).
Part of the Facebook Pages MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use fb_schedule_post to create or modify resources in Facebook Pages. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call fb_schedule_post repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Facebook Pages.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
fb_schedule_post:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Facebook Pages policy for all 28 tools.
Agents calling write-class tools like fb_schedule_post have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Schedule a post to be published at a future time. The scheduled_time must be between 10 minutes and 75 days from now (Unix timestamp in seconds).. It is categorised as a Write tool in the Facebook Pages MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for fb_schedule_post. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Facebook Pages MCP server.
fb_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 fb_schedule_post rule in your Intercept 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 Intercept policy for fb_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.
fb_schedule_post is provided by the Facebook Pages MCP server (node2flow/facebook-pages). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept