Checks how many of the 100 API-published posts per 24-hour limit have been used. Args: - ig_account_id (string): Instagram account ID Returns: Current usage and quota remaining.
AI agents call meta_check_instagram_publishing_limit to retrieve information from Meta 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 quota and usage metrics for an Instagram account. It performs no side effects, creates no content, executes no operations, and modifies no data. The sole purpose is to query and report current limit consumption, making it a straightforward Read operation with low severity risk.
From the tool's definition Tool name 'meta_check_instagram_publishing_limit' and description 'Checks how many of the 100 API-published posts per 24-hour limit have been used' indicate a query/retrieval operation that returns 'Current usage and quota remaining' without modifying any…
Documented attack patterns abuse exactly the kind of access meta_check_instagram_publishing_limit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_check_instagram_publishing_limit:
{
"version": "1",
"default": "deny",
"tools": {
"meta_check_instagram_publishing_limit": {}
}
} meta_check_instagram_publishing_limit 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.
Checks how many of the 100 API-published posts per 24-hour limit have been used. Args: - ig_account_id (string): Instagram account ID Returns: Current usage and quota remaining. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_check_instagram_publishing_limit: 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 Meta MCP Server. Nothing to install.
meta_check_instagram_publishing_limit 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 meta_check_instagram_publishing_limit 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 meta_check_instagram_publishing_limit. 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.
meta_check_instagram_publishing_limit is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, 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.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.