Searches for a hashtag and gets its ID, then retrieves top or recent media. Two-step process: first looks up the hashtag ID, then fetches media. Args: - ig_account_id (string): Instagram account ID (required for auth context) - hashtag (string): Hashtag to search (without #) - edge (string):
AI agents call meta_search_instagram_hashtag 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.
This tool only queries Meta's Instagram platform to look up hashtag metadata and fetch associated media content. It has no side effects, does not modify data, execute code, delete anything, or move money. The two-step process (lookup then fetch) remains within the Read category. Severity is low because hashtag search and media retrieval are informational queries with no blast radius if misused by an AI agent.
From the tool's definition Tool 'searches for a hashtag and gets its ID, then retrieves top or recent media' — pure retrieval operations with no modification or execution of commands. The description explicitly states it 'searches' and 'retrieves', which are read operations.
Documented attack patterns abuse exactly the kind of access meta_search_instagram_hashtag 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_search_instagram_hashtag:
{
"version": "1",
"default": "deny",
"tools": {
"meta_search_instagram_hashtag": {}
}
}meta_search_instagram_hashtag is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Searches for a hashtag and gets its ID, then retrieves top or recent media. Two-step process: first looks up the hashtag ID, then fetches media. Args: - ig_account_id (string): Instagram account ID (required for auth context) - hashtag (string): Hashtag to search (without #) - edge (string):. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_search_instagram_hashtag: 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_search_instagram_hashtag is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the meta_search_instagram_hashtag 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_search_instagram_hashtag. 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_search_instagram_hashtag 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.