Low Risk

meta_get_broadcast_channel_messages

Gets messages in an Instagram broadcast channel. Args: - channel_id (string): Broadcast channel ID - limit (number): Max messages (1–100, default 20) - after (string, optional): Pagination cursor Returns: Paginated list of messages with type, content, and timestamps.

How to control meta_get_broadcast_channel_messages ↓

What meta_get_broadcast_channel_messages does on Meta MCP Server

AI agents call meta_get_broadcast_channel_messages to retrieve information from Meta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why meta_get_broadcast_channel_messages needs a policy

This tool retrieves existing messages from a broadcast channel without modifying, deleting, or executing operations. It is a straightforward read operation with minimal risk—the worst case is exposure of message content the caller already has authorization to access via channel membership.

From the tool's definition Tool name 'meta_get_broadcast_channel_messages' and description 'Gets messages in an Instagram broadcast channel' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access meta_get_broadcast_channel_messages gives an agent:

How to control meta_get_broadcast_channel_messages

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_get_broadcast_channel_messages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "meta_get_broadcast_channel_messages": {}
  }
}

meta_get_broadcast_channel_messages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Meta MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about meta_get_broadcast_channel_messages

What does the meta_get_broadcast_channel_messages tool do? +

Gets messages in an Instagram broadcast channel. Args: - channel_id (string): Broadcast channel ID - limit (number): Max messages (1–100, default 20) - after (string, optional): Pagination cursor Returns: Paginated list of messages with type, content, and timestamps. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on meta_get_broadcast_channel_messages? +

Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_get_broadcast_channel_messages: 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.

What risk level is meta_get_broadcast_channel_messages? +

meta_get_broadcast_channel_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit meta_get_broadcast_channel_messages? +

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

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

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

Enforce policy on every Meta MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.