hide_thread_reply

Hide a reply on the brand’s Threads post (or unhide it with hide:false) — for spam and abuse moderation.

SERVERHermoso SOURCEhttps://app.hermoso.ai/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/hermoso/hide-thread-reply.md

WHAT IT DOES

What hide_thread_reply does on Hermoso

AI agents use hide_thread_reply to create or update resources in Hermoso, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hermoso environment.

RISK

Why hide_thread_reply is rated Medium

This tool modifies the visibility state of a reply (hide/unhide), which is a reversible write action. It does not delete content permanently — unhiding is possible — so it falls under Write rather than Destructive. Misuse could suppress legitimate user comments on a brand's public post, giving it medium severity.

From the tool's definition Hide a reply on the brand's Threads post (or unhide it with hide:false) — for spam and abuse moderation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hide_thread_reply safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hide_thread_reply, this is the rule to start with:

hide_thread_reply Rate-limited

hide_thread_reply 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hide_thread_reply": {
      "limits": [
        {
          "counter": "hide_thread_reply_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every hide_thread_reply call is checked against it from then on.

FAQ

Questions about hide_thread_reply

What does the hide_thread_reply tool do? +

Hide a reply on the brand’s Threads post (or unhide it with hide:false) — for spam and abuse moderation. It is categorised as a Write tool in the Hermoso MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on hide_thread_reply? +

Register the Hermoso MCP server in PolicyLayer and add a rule for hide_thread_reply: 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 Hermoso. Nothing to install.

What risk level is hide_thread_reply? +

hide_thread_reply is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hide_thread_reply? +

Yes. Add a rate_limit block to the hide_thread_reply 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.

How do I block hide_thread_reply completely? +

Set action: deny in the PolicyLayer policy for hide_thread_reply. 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.

What MCP server provides hide_thread_reply? +

hide_thread_reply is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hermoso, and thousands of servers like it.

This server

All 896 Hermoso tools →

Across the catalogue

reply-to-email on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →