Low Risk

get_user_posts

Get recent posts from an Instagram user. Args: username: Instagram username to get posts from. count: Maximum number of posts to return (default 12). Returns: A dictionary with success status and posts list.

How to control get_user_posts ↓

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

Low Risk

This tool retrieves publicly available Instagram post data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk, as the data returned is typically public information that users have already posted to Instagram.

From the tool's definition Tool name 'get_user_posts' and description 'Get recent posts from an Instagram user' indicate data retrieval with no modification or side effects. Returns 'a dictionary with success status and posts list' — a query operation.

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

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

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

get_user_posts 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 Instagram DM 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.

Go deeper

What does the get_user_posts tool do? +

Get recent posts from an Instagram user. Args: username: Instagram username to get posts from. count: Maximum number of posts to return (default 12). Returns: A dictionary with success status and posts list. It is categorised as a Read tool in the Instagram DM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_user_posts? +

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

What risk level is get_user_posts? +

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

Can I rate-limit get_user_posts? +

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

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

get_user_posts is provided by the Instagram DM MCP Server MCP server (trypeggy/instagram_dm_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Instagram DM MCP Server tool call.

Deterministic rules across all 25 Instagram DM MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

25 Instagram DM MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.