Hides or unhides a comment on an Instagram media object. Hidden comments are only visible to the comment author. This is a non-destructive alternative to deletion — useful for moderation. Args: - comment_id (string): Comment ID to hide/unhide - is_hidden (boolean): true to hide, false to unhide
AI agents use meta_hide_instagram_comment to create or update resources in Meta MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta MCP Server environment.
This tool modifies data state (comment visibility) reversibly without destroying it. The description explicitly notes it is 'non-destructive' and offers undo capability (unhide). This is characteristic of Write category tools.
From the tool's definition Tool description: 'Hides or unhides a comment on an Instagram media object.' The action is reversible (unhide via is_hidden=false parameter) and modifies comment visibility state rather than deleting data.
Documented attack patterns abuse exactly the kind of access meta_hide_instagram_comment 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_hide_instagram_comment:
{
"version": "1",
"default": "deny",
"tools": {
"meta_hide_instagram_comment": {
"limits": [
{
"counter": "meta_hide_instagram_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} meta_hide_instagram_comment 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.
Free to start. No card required.
Hides or unhides a comment on an Instagram media object. Hidden comments are only visible to the comment author. This is a non-destructive alternative to deletion — useful for moderation. Args: - comment_id (string): Comment ID to hide/unhide - is_hidden (boolean): true to hide, false to unhide. It is categorised as a Write tool in the Meta MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_hide_instagram_comment: 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_hide_instagram_comment 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 meta_hide_instagram_comment 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_hide_instagram_comment. 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_hide_instagram_comment 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.