hide_notification_context

Hide or unhide a notification context. Hidden contexts are omitted from list_notification_contexts unless includeHidden is true. Idempotent when the hidden state already matches.

SERVERHuly SOURCE@firfi/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/hide-notification-context.md

WHAT IT DOES

What hide_notification_context does on Huly

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

RISK

Why hide_notification_context is rated Medium

This tool modifies the visibility state of a notification context (hidden/unhidden), which is a reversible write operation. It does not delete data, execute code, or involve financial transactions. The blast radius is low since it only affects notification display preferences and is idempotent.

From the tool's definition Hide or unhide a notification context. Hidden contexts are omitted from list_notification_contexts unless includeHidden is true. Idempotent when the hidden state already matches.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hide_notification_context safely

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

hide_notification_context Rate-limited

hide_notification_context 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_notification_context": {
      "limits": [
        {
          "counter": "hide_notification_context_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 Huly, apply this rule, and every hide_notification_context call is checked against it from then on.

FAQ

Questions about hide_notification_context

What does the hide_notification_context tool do? +

Hide or unhide a notification context. Hidden contexts are omitted from list_notification_contexts unless includeHidden is true. Idempotent when the hidden state already matches. It is categorised as a Write tool in the Huly 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_notification_context? +

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

What risk level is hide_notification_context? +

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

Can I rate-limit hide_notification_context? +

Yes. Add a rate_limit block to the hide_notification_context 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_notification_context completely? +

Set action: deny in the PolicyLayer policy for hide_notification_context. 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_notification_context? +

hide_notification_context is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

The MCP Attack Database →

Guides

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