get_media_comments

THE RISK

Low Risk

Why get_media_comments needs a policy

This tool queries and fetches existing comment data from Instagram posts without creating, modifying, deleting, or executing operations. The capability is bounded (100 comments max) and inherently read-only.

From the tool's definition Tool retrieves comments from public Instagram posts/reels with 'Get up to 100 root comments' and 'internal pagination' — describes read-only data retrieval with no modification or deletion capability.

Risk signalsAdmin/system-level operation

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

POLICY

How to control get_media_comments

PolicyLayer is an MCP gateway — it sits between your AI agents and Instagram, and nothing reaches the server without passing your rules. This is the rule we recommend for get_media_comments:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_media_comments": {}
  }
}

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

Create a free account and register Instagram — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Instagram tools

Write download_media_content Download a reel or post to local files. Read rank_media_likers_by_followers Build a ranking of media likers sorted by follower count. Read download_media_audio Download the audio track from a reel or post. Read download_profile_highlights Download highlights for a profile, optionally filtered by title. Read download_profile_stories Download active stories for a profile. Read get_comment_likers Get users who liked a specific comment. Read get_comment_replies Get nested replies for a specific comment on a reel or post. Read get_followers_page Get one low-cost followers page for a profile.

All 43 Instagram tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_media_comments

What does the get_media_comments tool do? +

Get up to 100 root comments for an Instagram reel or post URL with internal pagination. It is categorised as a Read tool in the Instagram MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_media_comments? +

Register the Instagram MCP server in PolicyLayer and add a rule for get_media_comments: 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 Instagram. Nothing to install.

What risk level is get_media_comments? +

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

Can I rate-limit get_media_comments? +

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

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

get_media_comments is provided by the Instagram MCP server (lupikovoleg/instagram-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Instagram tool call.

Start from Instagram, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →