Medium Risk

fb_send_message

Send a text message via Messenger to a user. Requires the recipient PSID (Page-Scoped ID). Note: 24-hour messaging window applies — can only respond within 24h of the user's last message.

Part of the Facebook Pages MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

node2flow/facebook-pages Write Risk 2/5

AI agents use fb_send_message 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_send_message 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.

node2flow-facebook-pages.yaml
tools:
  fb_send_message:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Facebook Pages policy for all 28 tools.

Tool Name fb_send_message
Category Write
Risk Level Medium

View all 28 tools →

Agents calling write-class tools like fb_send_message have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the fb_send_message tool do? +

Send a text message via Messenger to a user. Requires the recipient PSID (Page-Scoped ID). Note: 24-hour messaging window applies — can only respond within 24h of the user's last message.. 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.

How do I enforce a policy on fb_send_message? +

Add a rule in your Intercept YAML policy under the tools section for fb_send_message. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Facebook Pages MCP server.

What risk level is fb_send_message? +

fb_send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit fb_send_message? +

Yes. Add a rate_limit block to the fb_send_message 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.

How do I block fb_send_message completely? +

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

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

Enforce policies on Facebook Pages

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.