instagram_create_post
Create and publish a post to Instagram. For a single image set media_type to IMAGE with image_url. For a single video/reel set media_type to REELS with video_url. For a carousel (2-10 images/videos in one post) set media_type to CAROUSEL and pass items[]; caption applies to the whole post. Image/...
This record as markdown: /tools/io-github-alifanov-scopegate/instagram-create-post.md
What instagram_create_post does on ScopeGate
AI agents use instagram_create_post to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why instagram_create_post is rated Medium
An AI agent can call instagram_create_post faster than any human can review: one bad instruction and it creates or modifies resources in ScopeGate by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs instagram_create_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For instagram_create_post, this is the rule to start with:
instagram_create_post stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every instagram_create_post call is checked against it from then on.
Questions about instagram_create_post
Create and publish a post to Instagram. For a single image set media_type to IMAGE with image_url. For a single video/reel set media_type to REELS with video_url. For a carousel (2-10 images/videos in one post) set media_type to CAROUSEL and pass items[]; caption applies to the whole post. Image/video URLs must be public. Note: Instagram allows up to 100 published posts per 24h. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for instagram_create_post: 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 ScopeGate. Nothing to install.
instagram_create_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the instagram_create_post 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 instagram_create_post. 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.
instagram_create_post is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue