pin_notification_context
Pin or unpin a notification context. Pinned contexts are highlighted in the inbox.
This record as markdown: /tools/dugynoo-huly-mcp/pin-notification-context.md
What pin_notification_context does on Huly
AI agents use pin_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.
Why pin_notification_context is rated Medium
This tool modifies user interface state and notification preferences in a reversible manner. It neither reads data without side effects (Read), executes arbitrary code (Execute), permanently destroys data (Destructive), nor involves financial transactions (Financial). The action of pinning/unpinning notifications is equivalent to updating a flag or preference, which is a classic Write operation.
From the tool's definition The tool 'pin_notification_context' performs a state modification action: it pins or unpins notification contexts, which changes how they are highlighted in the inbox. This is a reversible modification of data (pinning can be undone by unpinning).
Attacks that exploit this kind of access
The rule that runs pin_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 pin_notification_context, this is the rule to start with:
pin_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every pin_notification_context call is checked against it from then on.
Questions about pin_notification_context
Pin or unpin a notification context. Pinned contexts are highlighted in the inbox. 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.
Register the Huly MCP server in PolicyLayer and add a rule for pin_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.
pin_notification_context 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 pin_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.
Set action: deny in the PolicyLayer policy for pin_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.
pin_notification_context is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue