Sets the Messenger greeting text for a Facebook Page. This is shown to users before they send their first message. Requires: meta_list_pages called first to load page tokens. Args: - page_id (string): Facebook Page ID - greeting_text (string): The greeting text (max 160 characters)
AI agents use meta_set_greeting to create or update resources in Meta MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta MCP Server environment.
This tool creates or modifies data (greeting message configuration) in a reversible manner. It does not delete data (not Destructive), does not execute arbitrary code or external operations (not Execute), has no financial impact (not Financial), and only affects a single page's greeting display with minimal blast radius if misused.
From the tool's definition Tool description states it 'Sets the Messenger greeting text' - a write operation that modifies page configuration. The greeting is user-facing messaging that can be changed but is easily reversible (can be updated or cleared).
Documented attack patterns abuse exactly the kind of access meta_set_greeting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_set_greeting:
{
"version": "1",
"default": "deny",
"tools": {
"meta_set_greeting": {
"limits": [
{
"counter": "meta_set_greeting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}meta_set_greeting 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.
Sets the Messenger greeting text for a Facebook Page. This is shown to users before they send their first message. Requires: meta_list_pages called first to load page tokens. Args: - page_id (string): Facebook Page ID - greeting_text (string): The greeting text (max 160 characters). It is categorised as a Write tool in the Meta MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_set_greeting: 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 Meta MCP Server. Nothing to install.
meta_set_greeting 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 meta_set_greeting 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 meta_set_greeting. 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.
meta_set_greeting is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta 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.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.