Hide or unhide a comment from public view (less destructive than delete). WRITE OPERATION.
AI agents use hide_instagram_comment to create or update resources in Claude Meta — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Meta environment.
This tool modifies the visibility state of Instagram comments but does not permanently delete data. The reversibility (hide/unhide capability) and explicit 'WRITE OPERATION' classification in the description confirm this is a Write action.
From the tool's definition Tool description states 'Hide or unhide a comment from public view' and explicitly labels it as 'WRITE OPERATION.' The operation is reversible (can unhide), making it Write rather than Destructive.
Attacks that exploit this kind of access
Hide or unhide a comment from public view (less destructive than delete). WRITE OPERATION. It is categorised as a Write tool in the Claude Meta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Meta MCP server in PolicyLayer and add a rule for 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 Claude Meta. Nothing to install.
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 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 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.
hide_instagram_comment is provided by the Claude Meta MCP server (maxx3250/claude-meta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →