Get Instagram DM conversations.
AI agents call get_conversations to retrieve information from Instagram MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves direct message conversations from Instagram Business accounts without modifying, deleting, or executing any actions. While it accesses potentially sensitive communication data (DMs), the operation itself is read-only.
From the tool's definition Tool name 'get_conversations' and description 'Get Instagram DM conversations' indicate data retrieval with no modification or side effects. The verb 'Get' and retrieval context confirm a read-only operation.
Attacks that exploit this kind of access
Get Instagram DM conversations. It is categorised as a Read tool in the Instagram MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Instagram MCP Server MCP server in PolicyLayer and add a rule for get_conversations: 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 MCP Server. Nothing to install.
get_conversations 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 get_conversations 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 get_conversations. 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.
get_conversations is provided by the Instagram MCP Server MCP server (webnaresh/insta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_conversations is one line of Instagram MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →