Get one cursor-based page of profile reels. Use next_page_id from a previous page to continue.
AI agents call get_profile_reels_page to retrieve information from Instagram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves public Instagram profile reel data using cursor-based pagination. It performs no write, destructive, execute, or financial operations. While it accesses user data, the blast radius of misuse is limited to unauthorized data access rather than modification or system compromise. Classified as Read with low severity.
From the tool's definition Tool description states 'Get one cursor-based page of profile reels' - a retrieval operation with no modification, deletion, or execution of code. The verb 'Get' and the read-only nature of pagination through existing data confirm this is a query/fetch action.
Documented attack patterns abuse exactly the kind of access get_profile_reels_page gives an agent:
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_profile_reels_page:
{
"version": "1",
"default": "deny",
"tools": {
"get_profile_reels_page": {}
}
}get_profile_reels_page 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 one cursor-based page of profile reels. Use next_page_id from a previous page to continue. It is categorised as a Read tool in the Instagram MCP Server, which means it retrieves data without modifying state.
Register the Instagram MCP server in PolicyLayer and add a rule for get_profile_reels_page: 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.
get_profile_reels_page 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_profile_reels_page 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_profile_reels_page. 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_profile_reels_page 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.
Start from Instagram, 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.
43 Instagram tools catalogued and risk-classified — across an index of 43,000+ MCP servers.