Get Instagram stories from a user. Args: username: Instagram username to get stories from. Returns: A dictionary with success status and stories information.
AI agents call get_user_stories 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.
This tool queries and retrieves publicly or semi-publicly available Instagram stories without altering state or triggering side effects. It is a straightforward read operation. While accessing user data carries minor privacy concerns, the tool itself performs no destructive, executable, or financial actions. Severity is low because misuse would only expose already-shared user content.
From the tool's definition Tool name 'get_user_stories' and description state it 'Get Instagram stories from a user' with return of 'stories information'. No modification, deletion, or execution of code occurs—purely retrieval of accessible user content.
Documented attack patterns abuse exactly the kind of access get_user_stories 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_stories:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_stories": {}
}
}get_user_stories 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.
Get Instagram stories from a user. Args: username: Instagram username to get stories from. Returns: A dictionary with success status and stories information. It is categorised as a Read tool in the Instagram DM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Instagram DM MCP Server MCP server in PolicyLayer and add a rule for get_user_stories: 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.
get_user_stories 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_user_stories 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_user_stories. 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_user_stories 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.
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.